CVE-2024-0681 Page Restriction WordPress (WP) – Protect WP Pages/Post <= 1.3.4 - Protection Mechanism Bypass
Unauthenticated attackers can view private pages via the REST API due to missing access controls in the Page Restriction WordPress plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-0681?
CVE-2024-0681 is a medium-severity vulnerability in cyberlord92 Page and Post Restriction, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-693
Which versions are affected by CVE-2024-0681?
It affects 1 product.
Products include Miniorange Page Restriction.
How do I fix CVE-2024-0681?
No fix has been published for CVE-2024-0681 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-0681 being exploited?
There is no known exploitation of CVE-2024-0681 in the wild and no public exploit code.
Other vulnerabilities in cyberlord92 Page and Post Restriction
Sources
Also known as GHSA-ccwc-7pw8-r82c.