Page Restriction Wordpress (Wp) – Protect Wp Pages/Post
Approved changes feed: RSS · Atom
cpe:2.3:a:cyberlord92:page_restriction_wordpress_(wp)_–_protect_wp_pages/post:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Cyberlord92 (d4db5aca-fcb6-5704-b2d9-5b8ecb1765d8) |
|---|---|
| Product | Page Restriction Wordpress (Wp) – Protect Wp Pages/Post (cda31daa-de1d-5a0f-ac94-6e4c4e1e8dc5) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-0681 |
vulnerable | 2026-06-03 14:54:03.253438 |
Page Restriction WordPress (WP) – Protect WP Pages/Post <= 1.3.4 - Protection Mechanism Bypass
MEDIUM (5.3)
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.
Published: 2024-03-13T15:27:08.355Z
Updated: 2026-04-08T17:12:54.551Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.