PatchSiren cyber security CVE debrief
CVE-2026-78153 Restrict User Access CVE debrief
The Restrict User Access WordPress plugin before 2.8.1 does not normalise the REST API route before checking it against the routes its content protection covers, allowing unauthenticated users to bypass that protection and read restricted content and enumerate users. This vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. The vulnerability is caused by the plugin's failure to normalize the REST API route before checking it against the routes its content protection covers. Affected product deployments should be reviewed and assessed for potential operational impact. Operators, platform administrators, and security teams should verify the version of the plugin and update to 2.8.1 or later if necessary. Further verification is recommended to confirm the vulnerability's existence and impact.
- Vendor
- Restrict User Access
- Product
- Restrict User Access
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-02
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-09-02
- Advisory updated
- 2026-09-03
Who should care
WordPress administrators and users of the Restrict User Access plugin should be aware of this vulnerability and take necessary actions to protect their sites. It is essential for operators, platform administrators, and security teams to review the affected product deployments and assess the potential operational impact. They should also verify the version of the plugin and update to 2.8.1 or later if necessary.
Technical summary
The Restrict User Access WordPress plugin before 2.8.1 is vulnerable to unauthorized access, allowing unauthenticated users to bypass content protection and read restricted content and enumerate users. This vulnerability has a CVSS score of 5.3 and is classified as MEDIUM severity. The vulnerability is caused by the plugin's failure to normalize the REST API route before checking it against the routes its content protection covers.
Defensive priority
Medium priority due to the CVSS score of 5.3 and the potential for unauthorized access to restricted content.
Recommended defensive actions
- Verify the version of the Restrict User Access WordPress plugin and update to 2.8.1 or later if necessary.
- Review and restrict access to sensitive content and user enumeration.
- Monitor for potential unauthorized access attempts.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The evidence for this vulnerability is based on the NVD vulnerability detail and a source reference from WPScan. Further verification is recommended to confirm the vulnerability's existence and impact. It is essential to review the official CVE record and NVD detail page for accurate information. Additionally, defenders should verify the affected product deployments in managed environments and assess the potential operational impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-78153 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-78153
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-78153 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-78153
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/d17c00fc-002a-4f5f-9255-dcc34da89d90/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.