CVE-2026-5617 HIGH

CVE-2026-5617: Login as User <= 1.0.3 - Authenticated (Subscriber+) Privilege Escalation via 'oclaup_original_admin' Cookie

Vendor Royalnavneet
Product Login as User – Switch User & WooCommerce Login as Customer
Weakness CWE-639 · IDOR
Published April 15, 2026
Last update April 15, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

A low-privilege user can read, modify, or delete data across the site, including other users' accounts and WooCommerce customer information. The vulnerability exists in versions up to 1.0.1 of the Login as User plugin. An authenticated user with basic permissions can exploit this without additional user interaction. Site administrators should update immediately to a version newer than 1.0.1.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete sensitive data including other users' accounts and WooCommerce customer records.

Potential impact on your site

04Site Impact

Any authenticated user can access and modify other users' data, compromising customer privacy and site integrity.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site; no additional user interaction required.

Key dates

06Disclosure timeline

April 15, 2026 CVE published
April 15, 2026 Record updated