Subscriber-level content disclosure via unguarded REST routes
Published Aug 14, 2025 · Updated Aug 14, 2025
Access-control bypass in PPWP – Password Protect Pages before 1.9.11 allows remote authenticated users to read protected content via REST. With sitewide password protection enabled, the plugin fails to apply its password gate to WordPress posts REST routes and returns protected post bodies to subscriber sessions. A subscriber-level account and sitewide protection are required; the demonstrated effect is content disclosure without modification or service interruption.
Summary
What happened
Access-control bypass in PPWP – Password Protect Pages before 1.9.11 allows remote authenticated users to read protected content via REST. With sitewide password protection enabled, the plugin fails to apply its password gate to WordPress posts REST routes and returns protected post bodies to subscriber sessions. A subscriber-level account and sitewide protection are required; the demonstrated effect is content disclosure without modification or service interruption.
The record
- CVE
- CVE-2025-5998
- Published
- Aug 14, 2025
- Updated
- Aug 14, 2025
- Vendor
- WP Folio Team
- Product
- PPWP – Password Protect Pages
- Classifications
- CWE-280, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 14, 2025CVE publishedPublication date reported by the CVE source.
- Aug 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.9.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- WPScan subscriber REST API proof of conceptproof of concept · validated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo