First published: Wed Mar 13 2024(Updated: )
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.
Credit: security@wordfence.com
Affected Software | Affected Version | How to fix |
---|---|---|
WordPress Protect WP Pages/Post | <=1.3.4 | |
MiniOrange Page Restriction WordPress | <1.3.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-0681 is considered a moderate severity vulnerability due to its potential for information disclosure.
To fix CVE-2024-0681, update the Page Restriction WordPress plugin to version 1.3.5 or later.
CVE-2024-0681 can disclose private pages and posts via the REST API due to improper access restrictions.
CVE-2024-0681 affects all versions of the Page Restriction WordPress plugin up to and including 1.3.4.
The impact of CVE-2024-0681 on site security includes unauthorized access to private content, potentially exposing sensitive information.