CVE-2026-18786 - Authentication Error Raised For Any Request Whose Uri Merely Contains A Checkview Plugin
CVE-2026-18786
The CheckView WordPress plugin before 2.3.2 does not restrict its REST API authentication filter to its own routes and unconditionally discards the authentication error raised for any request whose URI merely contains a CheckView WordPress plugin before 2.3.2-specific string, making it possible for unauthenticated attackers to bypass the REST nonce check and perform any REST action available to a logged-in administrator, such as creating a new administrator account, via a crafted link an administrator is tricked into opening.
CVE-2026-18786
UNKNOWN
CVSS 0.0
Published 2026-08-10
Updated 2026-08-10
AI Risk Low (6/100)
Active Exploit: No strong signal
Published Exploit: No public exploit references
Priority: P5 Monitor
Severity Band
UNKNOWN
CVSS Vector
Unspecified
Affected Components
3
Reference Links
1
AI Risk Engine
Low (6/100)
Exploitability
Low
Active Exploitation
No strong signal
Published Exploit Status
No public exploit references
AI Context
Machine-generated threat intelligence
AI
Updated just now
AI enriched just now (2026-08-10 21:57 UTC)
Technical Summary
The CheckView WordPress plugin before 2.3.2 does not restrict its REST API authentication filter to its own routes and unconditionally discards the authentication error raised for any request whose URI merely contains a CheckView WordPress plugin before 2.3.2-specific string, making it possible for unauthenticated attackers to bypass the REST nonce check and perform any REST action available to a logged-in administrator, such as creating a new administrator account, via a crafted link an administrator is tricked into opening.
Potential Impact
Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as Low based on low-bar exploit prerequisites.
Primary risk drivers: low-bar exploit prerequisites
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
AI risk score 6/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.