Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain subscriber account via registration
-
DeliverySet oclaup_original_admin cookie to admin user ID
-
ExploitTrigger Return to Admin function
-
ExecutionPlugin authenticates as administrator
-
ImpactExecute admin-level actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Requires WordPress with Login as User plugin versions up to 1.0.3 installed and activated. Attacker must be authenticated as Subscriber or above. No user interaction needed. Attacker crafts malicious oclaup_original_admin cookie to escalate to administrator without server-side verification. |
| Impact | This vulnerability presents elevated real-world risk despite requiring authenticated access. The CVSS 8.8 (High) score reflects network-based attack vector (AV:N), low attack complexity (AC:L), low privileges required (PR:L - subscriber level), no user interaction (UI:N), and high impact across confidentiality, integrity, and availability (C:H/I:H/A:H). The unchanged scope (S:U) indicates the vulnerability affects only the WordPress application, but complete admin takeover enables full site compromise. The low barrier to exploitation is concerning: WordPress subscriber accounts are often freely obtainable through self-registration on many sites, and the attack requires only basic HTTP cookie manipulation-no special tools or deep technical knowledge. EPSS data is unavailable, but the simplicity of exploitation (cookie manipulation) combined with the widespread use of WordPress and user-switching plugins suggests moderate exploitation probability if the plugin has significant installations. No CISA KEV listing or public exploit identified, indicating this is not yet widely exploited, but the straightforward attack path (evident from Wordfence's detailed source code references to lines 45 and 50 in class-login-handler.php) makes weaponization trivial for moderately skilled attackers. The SSVC framework would classify this as having confirmed exploitation potential (proof-of-concept level understanding from researcher disclosure), likely automatable (cookie manipulation is easily scripted), and total technical impact (full admin control). Priority depends on whether the plugin is installed; if present, immediate remediation is critical. |
| Exploit ScenarioDerived | An attacker registers a free subscriber account on a WordPress site running the vulnerable Login as User plugin. Using browser developer tools or a proxy like Burp Suite, they set a cookie named 'oclaup_original_admin' with the value '1' (the typical admin user ID in WordPress). The attacker then navigates to or crafts a request that triggers the plugin's 'Return to Admin' functionality, which calls handle_return_to_admin(). The plugin reads the forged cookie value without verification and authenticates the attacker as user ID 1-the site administrator. The attacker now has full administrative control, enabling them to install malicious plugins, modify site content, create backdoor accounts, steal sensitive data, or completely deface the website. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 15, 2026
Privilege escalation in Login as User WordPress plugin (all versions ≤1.0.3) allows authenticated subscribers to become administrators by manipulating a client-side cookie. Attackers with Subscriber-level access can set the 'oclaup_original_admin' cookie to an admin user ID and trigger the 'Return to Admin' function, granting full admin privileges. CVSS 8.8 (High) with network vector, low complexity, and low privileges required. No public exploit identified at time of analysis, EPSS data not available. Wordfence reported vulnerability with direct source code references to vulnerable functions in class-login-handler.php.
RemediationAI
Immediately update the Login as User plugin to a patched version newer than 1.0.3 if available through the WordPress plugin repository at https://wordpress.org/plugins/one-click-login-as-user/. Check the Wordfence threat intelligence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/c0c74d48-6cfc-4899-bd2c-4a80b1f6e05f?source=cve for the latest remediation guidance and confirmed fix version. If no patched version is available, immediately deactivate and remove the plugin until a secure update is released. As a temporary workaround, restrict user registration to prevent unauthorized subscriber account creation, and audit existing subscriber accounts for suspicious activity. Review WordPress user audit logs for unexpected privilege escalations or admin account access from lower-privileged users. Consider alternative user-switching plugins with established security track records and active maintenance. Implement web application firewall (WAF) rules to monitor for suspicious cookie manipulation attempts targeting the 'oclaup_original_admin' cookie parameter until the plugin can be patched or replaced.
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 vulnerability exists in the handle_return_to_admin() function within the Login as User WordPress plugin (CPE: cpe:2.3:a:royalnavneet:login_as_user_-_switch_user_&_woocommerce_login_as_customer). The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key), where the plugin implicitly trusts the client-controlled cookie 'oclaup_original_admin' to determine user authentication context during admin-to-user switching operations. The vulnerable code fails to implement server-side verification that the cookie value was legitimately set during an authorized admin-initiated user switch session. The plugin's intended functionality allows administrators to impersonate other users for testing or support purposes, with a 'Return to Admin' feature to restore the original admin session. However, the implementation stores the original admin user ID in a client-side cookie without cryptographic protection, session binding, or validation that the current user actually originated from an admin session. An attacker can forge this cookie with any admin user ID, and the plugin will authenticate them as that administrator when the return function is invoked.
Know when Login As User Switch User Woocommerce Login As Customer 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:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
The Login as User plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.3. This is due to the handle_return_to_admin() function trusting a client-controlled cookie (oclaup_original_admin) to determine which user to authenticate as, without any server-side verification that the cookie value was legitimately set during an admin-initiated user switch. This makes it possible for authenticated attackers, with Subscriber-level access and above, to escalate their privileges to administrator by setting the oclaup_original_admin cookie to an administrator's user ID and triggering the "Return to Admin" functionality.
Executive ViewAI
The Login as User WordPress plugin versions 1.0.3 and earlier contain a critical privilege escalation vulnerability that allows any subscriber-level user to gain full administrator access through cookie manipulation. Organizations running this plugin face immediate risk of unauthorized administrative control, data breach, and website compromise affecting all WordPress sites using affected versions.
Immediate interim mitigations: (1) Disable the 'Return to Admin' functionality if plugin configuration allows; (2) Restrict Subscriber role assignment to trusted users only and audit existing subscribers; (3) Implement Web Application Firewall rules to block requests containing 'oclaup_original_admin' cookie manipulation; (4) Enable detailed WordPress audit logging to detect privilege escalation attempts. No vendor-released patch identified at time of analysis-plugin removal or replacement is the primary remediation path.
Threat Intelligence Overview
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-22844
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB