Security readout for executives and security teams
Plain-English summary
A WordPress plugin meant to restrict page access can fail through the WordPress REST API. On affected sites, unauthenticated visitors may read content that site owners intended to keep private. The impact is confidentiality exposure, not code execution or service outage.
Executive priority
Treat this as a targeted confidentiality risk for WordPress sites, not an infrastructure emergency. Prioritize sites where restricted pages hold customer data, private business information, paid content, or unpublished material.
Technical view
Simple Page Access Restriction for WordPress is reported vulnerable through version 1.0.21. The issue is improper access control via REST API, mapped to CWE-284, with CVSS 3.1 score 5.3. The source bundle states unauthenticated attackers can bypass page restrictions and view page content.
Likely exposure
Exposure is limited to WordPress sites using Simple Page Access Restriction up to and including 1.0.21, especially where restricted pages contain sensitive internal, customer, or pre-publication content.
Exploitation context
The source bundle does not report CISA KEV listing or active exploitation. The vulnerability is remotely reachable, unauthenticated, low complexity, and requires no user interaction, but the documented impact is limited to low confidentiality loss.
Researcher notes
Evidence supports improper access control through REST API for Simple Page Access Restriction through 1.0.21. The bundle includes a WordPress.org changeset reference, but does not clearly state a fixed version. Avoid assuming exploitation in the wild without additional sourced evidence.
Mitigation direction
- Inventory WordPress sites for Simple Page Access Restriction and record plugin versions.
- If using version 1.0.21 or earlier, check vendor and Wordfence guidance for fixed release status.
- Update the plugin when a vendor-supported fixed version is available.
- Temporarily disable or replace the plugin if sensitive restricted pages depend on it.
- Remove sensitive content from restricted pages until access control is verified.
Validation and detection
- Confirm whether the plugin is installed on each WordPress property.
- Identify pages whose confidentiality depends on this plugin's restrictions.
- Review access logs for unauthenticated REST requests involving restricted content.
- In staging, verify restricted content is not exposed through WordPress REST responses.
- Document compensating controls if no fixed version is confirmed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-0965 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.