Protected-post disclosure via unenforced REST API restrictions
Published Feb 28, 2024 · Updated Apr 8, 2026
Information disclosure in Page Restrict 2.5.5 and earlier allows remote attackers to read protected posts through the WordPress REST API. The plugin's access-control logic does not enforce its page restrictions when WordPress serves a private post through a REST API request. No authentication or user interaction is required; exposure is limited to content that site administrators intended the plugin to protect.
Summary
What happened
Information disclosure in Page Restrict 2.5.5 and earlier allows remote attackers to read protected posts through the WordPress REST API. The plugin's access-control logic does not enforce its page restrictions when WordPress serves a private post through a REST API request. No authentication or user interaction is required; exposure is limited to content that site administrators intended the plugin to protect.
The record
- CVE
- CVE-2024-0682
- Published
- Feb 28, 2024
- Updated
- Apr 8, 2026
- Vendor
- Andy Stratton
- Product
- Page Restrict
- Classifications
- CWE-693, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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 <=2.5.5
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
No public exploit references are available in this record.
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