WP Private Content Plus <= 3.6.2 - Unauthenticated Sensitive Information Exposure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WP Private Content Plus
- Affected Version
<= 3.6.2- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-4390
At a glance
CVE-2025-4390 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor 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 August 2025, reported by Luca Epifanio (Bitcube Security).
Vulnerability Overview
The WP Private Content Plus plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.6.2 via the 'validate_restrictions' function. This makes it possible for unauthenticated attackers to extract sensitive data including the content of resticted posts on archive and feed pages.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
WP Private Content Plus <= 3.6.2 carries this weakness at validate_restrictions, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. 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
Same weakness class
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-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