Community by PeepSo <= 6.1.6.0 - Cross-Site Request Forgery via delete
Strategic Overview
- Status
- Patched in 6.2.0.0
- Affected Plugin
- Community by PeepSo – Download from PeepSo.com
- Affected Version
<= 6.1.6.0- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-39925
At a glance
CVE-2023-39925 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Community by PeepSo WordPress plugin, affecting versions <= 6.1.6.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.2.0.0; sites on affected versions should update now. Disclosed November 2023, reported by Revan Arifio.
Vulnerability Overview
The Community by PeepSo plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.1.6.0. This is due to missing or incorrect nonce validation on the delete function. This makes it possible for unauthenticated attackers to delete PeepSo posts 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)
Reaching this weakness in Community by PeepSo <= 6.1.6.0 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.2.0.0: builds <= 6.1.6.0 are affected, anything from 6.2.0.0 onward is not.
Remediation
Update to version 6.2.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.2.0.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Community by PeepSo – Download from PeepSo.com
- 8.8CVE-2016-10968: Community by PeepSo Privilege Escalation
CVE-2016-10968 - 6.5CVE-2026-66668: Community by PeepSo SQL Injection
CVE-2026-66668 - 6.5CVE-2024-25923: Community by PeepSo <= 6.2.7.0 Info Disclosure
CVE-2024-25923 - 6.4CVE-2023-47850: Community by PeepSo <= 6.2.2.0 Stored XSS
CVE-2023-47850 - 6.1CVE-2024-11447: Community by PeepSo Reflected XSS
CVE-2024-11447 - 6.1CVE-2024-0187: Community by PeepSo <= 6.3.1.1 Reflected XSS
CVE-2024-0187 - 6.1CVE-2023-48746: Community by PeepSo <= 6.2.6.0 Reflected XSS
CVE-2023-48746 - 5.4CVE-2024-9873: Community by PeepSo <= 6.4.6.1 Stored XSS
CVE-2024-9873
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C