CVE-2026-14943: Password Protected < 2.8.4 - Unauthenticated Sensitive Information Exposure via REST API
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
wordpress-plugin/Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Contentto a version that resolves this vulnerability.Fixed in 2.8.4 - Upgrade
Upgrade
wordpress-plugin/Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Contentto a version that resolves this vulnerability.Fixed in 2.6.7
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14943?
CVE-2026-14943 has a risk score of 55, indicating a moderate severity level.
How do I fix CVE-2026-14943?
To fix CVE-2026-14943, update the Password Protected plugin to version 2.8.4 or later.
What does CVE-2026-14943 expose?
CVE-2026-14943 allows unauthenticated visitors to access sensitive information via the REST API.
Which versions of the Password Protected plugin are affected by CVE-2026-14943?
CVE-2026-14943 affects versions of the Password Protected plugin prior to 2.8.4.
What type of vulnerability is CVE-2026-14943 categorized as?
CVE-2026-14943 is categorized as an information leak vulnerability (CWE-200).