CVE-2023-32092

Community by PeepSo <= 6.0.9.0 - Cross-Site Request Forgery to Field Duplication

2023-05-12 00:00
Skalucy

Strategic Overview

Status
Patched in 6.1.0.0
Affected Version
<= 6.0.9.0
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-32092
View all Community by PeepSo – Download from PeepSo.com vulnerabilities

At a glance

CVE-2023-32092 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Community by PeepSo WordPress plugin, affecting versions <= 6.0.9.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.1.0.0; sites on affected versions should update now. Disclosed May 2023, reported by Skalucy.

Vulnerability Overview

The Community by PeepSo plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.0.9.0. This is due to missing or incorrect nonce validation on the duplicate_field() function. This makes it possible for unauthenticated attackers to duplicate user fields via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Community by PeepSo <= 6.0.9.0 carries this weakness at duplicate_field(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Community by PeepSo the fix is 6.1.0.0: builds <= 6.0.9.0 are affected, anything from 6.1.0.0 onward is not.

Remediation

Update to version 6.1.0.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Community by PeepSo: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Community by PeepSo 6.1.0.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C