CVE-2024-0681 MEDIUM

CVE-2024-0681: Page Restriction WordPress (WP) – Protect WP Pages/Post <= 1.3.4 - Protection Mechanism Bypass

Vendor Cyberlord92
Product Page and Post Restriction
Weakness CWE-693
Published March 13, 2024
Last update April 8, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Page and Post Restriction versions 1.3.4 and earlier contain a flaw that allows unauthenticated attackers to read sensitive information over the network. The vulnerability requires no user interaction and can be exploited remotely. Site administrators should update to a version newer than 1.3.4 to mitigate exposure.

What an attacker can do

03Attacker Capabilities

Read sensitive information from the site without authentication.

Potential impact on your site

04Site Impact

Confidential data may be exposed to unauthenticated visitors without your knowledge.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

March 13, 2024 CVE published
April 8, 2026 Record updated