WP Private Content Plus <= 3.1 - Cross-Site Request Forgery Bypass
Strategic Overview
- Status
- Patched in 3.2
- Affected Plugin
- WP Private Content Plus
- Affected Version
<= 3.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2021-4385
At a glance
CVE-2021-4385 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Private Content Plus WordPress plugin, affecting versions <= 3.1. 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 3.2; sites on affected versions should update now. Disclosed March 2021, reported by Jerome Bruandet.
Vulnerability Overview
The WP Private Content Plus plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1. This is due to missing or incorrect nonce validation on the save_groups() function. This makes it possible for unauthenticated attackers to add new group members 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)
WP Private Content Plus <= 3.1 carries this weakness at save_groups(), 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 WP Private Content Plus the fix is 3.2: builds <= 3.1 are affected, anything from 3.2 onward is not.
Remediation
Update to version 3.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Private Content Plus: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Private Content Plus 3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in WP Private Content Plus
- 7.5CVE-2019-15816: WP Private Content Plus <= 1.31 Settings Change
CVE-2019-15816 - 5.3CVE-2025-10720: WP Private Content Plus <= 3.6.2 Information Exposure
CVE-2025-10720 - 5.3CVE-2025-4390: WP Private Content Plus <= 3.6.2 Info Exposure
CVE-2025-4390 - 5.3CVE-2024-11292: WP Private Content Plus Content Restriction Bypass
CVE-2024-11292 - 5.3CVE-2024-0680: WP Private Content Plus Protection Mechanism Bypass
CVE-2024-0680 - 4.4WP Private Content Plus <= 3.4 Stored Cross-Site Scripting
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C