Page Restriction WordPress (WP) – Protect WP Pages/Post: Sensitive information exposure
Page Restriction WordPress (WP) – Protect WP Pages/Post is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.
- Component
- Page Restriction WordPress (WP) – Protect WP Pages/Post
- Plugin slug
page-restriction- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Mar 13, 2024
This CVE was published Mar 13, 2024 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Page Restriction WordPress (WP) – Protect WP Pages/Post to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N