Description
The Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content WordPress plugin before 2.8.4 does not restrict REST API access to authenticated users when a specific option is enabled, allowing unauthenticated visitors to bypass the sitewide password gate and read otherwise-protected content and account identifiers via the REST API. This re-introduces a previously-fixed issue (CVE-2024-0437), which was patched in 2.6.7 and regressed in 2.6.8.
Published: 2026-08-07
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Password Protected plugin for WordPress, in versions prior to 2.8.4, does not enforce authentication on its REST API when the "Enable password protection" option is active. This allows any unauthenticated visitor to send REST requests and retrieve protected content such as pages, posts, categories, or partial content, as well as account identifiers. The flaw effectively bypasses the sitewide password gate, exposing sensitive information to the public. The weakness is a case of improper authorization (CWE‑284) leading to sensitive information disclosure (CWE‑200).

Affected Systems

The vulnerability affects the Password Protected WordPress plugin across all WordPress installations using any version older than 2.8.4. Versions 2.6.7 and earlier fixed the issue, but 2.6.8 regressed it, so any site running 2.6.8 or earlier, except 2.6.7, is vulnerable. Administrators should examine the installed plugin version and upgrade if necessary.

Risk and Exploitability

Because the REST API is publicly reachable, an attacker does not need any credentials to exploit the flaw. The errant API endpoints return content that would normally be hidden behind the password protection. No explicit CVSS score is listed in the data, but the exposure of privileged content is a high‑severity risk. EPSS is not available, and the vulnerability is not currently listed in CISA KEV, yet the ease of exploitation warrants urgent attention.

Generated by OpenCVE AI on August 7, 2026 at 07:26 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Password Protected plugin to version 2.8.4 or later, which restores proper authentication checks on the REST API.
  • If an immediate upgrade is not possible, disable the REST API feature for the plugin or remove the sitewide password protection until a patched version is available.
  • Verify that WordPress REST API endpoints are protected at the application level and monitor incoming requests for unauthorized activity.

Generated by OpenCVE AI on August 7, 2026 at 07:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 07 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-284

Fri, 07 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
Description The Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content WordPress plugin before 2.8.4 does not restrict REST API access to authenticated users when a specific option is enabled, allowing unauthenticated visitors to bypass the sitewide password gate and read otherwise-protected content and account identifiers via the REST API. This re-introduces a previously-fixed issue (CVE-2024-0437), which was patched in 2.6.7 and regressed in 2.6.8.
Title Password Protected < 2.8.4 - Unauthenticated Sensitive Information Exposure via REST API
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-07T06:00:10.727Z

Reserved: 2026-07-07T12:05:19.128Z

Link: CVE-2026-14943

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T07:30:09Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-284

    Improper Access Control