EUVD-2026-90851
GHSA-jhwc-r696-2xmf
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running vulnerable Authorizer plugin
-
DeliverySend crafted unauthenticated request
-
ExploitAbuse incorrect privilege assignment
-
ExecutionObtain elevated/admin privileges
-
PersistInstall backdoor or edit theme for RCE
-
ImpactFull site and data compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Requires a WordPress site with the Authorizer plugin installed at version 3.15.3 or earlier. Per the provided vector (PR:N/UI:N) no authentication or user interaction is needed and exploitation is remote over the network against affected installations; however the description is terse and does not name the specific endpoint, parameter, or whether a particular authentication backend (LDAP/CAS/OAuth/Google) must be configured - confirm with Patchstack whether 'unauthenticated' is literal or requires a low-privileged account. The primary limiting factor is the product's low deployment footprint rather than any stated configuration precondition. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8 CRITICAL) describes a remote, unauthenticated, low-complexity privilege escalation with full confidentiality/integrity/availability impact - in WordPress terms, an attacker promoting themselves to or acting with elevated (likely administrator) privileges with no credentials and no user interaction. If accurate, this is the most dangerous class of plugin flaw because admin access on a WordPress site generally equals full site compromise and often server-side code execution via plugin/theme editing. However, the decision signals are thin: no EPSS probability, no CISA KEV listing (no public exploit identified at time of analysis), no POC, and no SSVC data are provided. The sole reference is a single Patchstack database entry, so severity rests entirely on one vendor's assessment with no NVD corroboration or independent vector confirmation. The CWE-266 (Incorrect Privilege Assignment) classification is consistent with privilege escalation. The practical tension to verify: the description asserts 'Unauthenticated' and the vector carries PR:N, but many WordPress privilege-escalation flaws require at least a low-privileged/registered account or a specific authentication backend to be enabled; defenders should confirm with Patchstack whether PR:N is literal or whether some foothold/configuration is needed. Treat as high-priority for patching given the product's security-sensitive role (it governs authentication) despite the absence of exploitation telemetry. |
| Exploit ScenarioDerived | An attacker sends crafted requests to a WordPress site running the Authorizer plugin (<= 3.15.3), abusing the flawed privilege-assignment logic to gain elevated privileges without valid credentials. With administrator-level access they install a malicious plugin or edit theme files to achieve code execution and full site takeover. No public exploit code or active exploitation has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated privilege escalation in the Authorizer WordPress plugin (versions up to and including 3.15.3) allows remote attackers to gain elevated privileges, potentially administrator-level, on affected WordPress sites. The vulnerability carries a CVSS 3.1 base score of 9.8 (critical) and per the vector requires no authentication or user interaction. No public exploit code has been identified at the time of analysis, but the low deployment footprint of the plugin may limit widespread exploitation.
RemediationAI
No vendor-released patch version is specified in the provided data; consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/authorizer/vulnerability/wordpress-authorizer-plugin-3-15-3-privilege-escalation-vulnerability) for updates. As an immediate compensating control, disable or uninstall the Authorizer plugin until a patched version is available; this will break external authentication for users relying on LDAP, CAS, OAuth, or Google, but it eliminates the vulnerability. If the plugin must remain active, restrict access to its authentication endpoints via IP allowlisting or web application firewall (WAF) rules, though this may not be fully effective if the flaw resides in a publicly accessible function and could block legitimate users. Additionally, monitor WordPress user accounts for unauthorized role changes or new administrator accounts, and audit logs for suspicious activity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Authorizer plugin is a WordPress authentication extension by Paul Ryan that integrates external identity providers such as LDAP, CAS, OAuth, and Google. The vulnerability class is CWE-266 (Incorrect Privilege Assignment), meaning the plugin fails to properly assign or validate user privileges, likely during the authentication or role-synchronization process. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) confirms a remotely exploitable, unauthenticated attack with full confidentiality, integrity, and availability impact, enabling an attacker to elevate their privileges to an administrative level. The exact vulnerable endpoint, parameter, or required authentication backend (e.g., LDAP, CAS) is not detailed in the available Patchstack reference, so the literal 'unauthenticated' condition should be confirmed with the vendor. The CPE string cpe:2.3:a:paul_ryan:authorizer:*:*:*:*:*:*:*:* indicates all versions are potentially affected, but the advisory specifically notes versions up to and including 3.15.3.
Know when Authorizer gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Accepting the description's 'unauthenticated' claim gives PR:N/UI:N over the network; privilege escalation to admin yields full C:H/I:H/A:H, so AC:L and base 9.8.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Privilege Escalation in Authorizer <= 3.15.3 versions.
Executive ViewAI
The Authorizer WordPress plugin (versions up to 3.15.3) contains a critical unauthenticated privilege escalation vulnerability (CVE-2026-103752) that could allow attackers to gain administrator-level access to affected WordPress sites. Organizations using this plugin face potential full site compromise, including data theft, defacement, and use of the site as a pivot point for further attacks. Leadership should act urgently because no vendor patch is currently available.
No vendor patch identified at time of analysis. Interim mitigations include disabling the Authorizer plugin, implementing WAF virtual patching rules to block exploitation attempts, restricting admin access, enforcing multi-factor authentication, and monitoring for unauthorized privilege changes.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Exploit-DB