WP Private Content Plus <= 3.6.2 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP Private Content Plus
- Affected Version
<= 3.6.2- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2025-10720
At a glance
CVE-2025-10720 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Private Content Plus WordPress plugin, affecting versions <= 3.6.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed September 2025, reported by Lorenzo Camilli.
Vulnerability Overview
The WP Private Content Plus plugin for WordPress is vulnerable to information exposure in all versions up to, and including, 3.6.2. This is due to the plugin relying on an easily settable cookie to provide access to password protected posts. This makes it possible for unauthenticated attackers to view private content without a valid password.
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, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in WP Private Content Plus <= 3.6.2 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. No fixed build of this plugin is recorded for WP Private Content Plus yet, so installs running <= 3.6.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- 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-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
- 4.3CVE-2021-4385: WP Private Content Plus <= 3.1 CSRF Bypass
CVE-2021-4385
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C