royalnavneet Login as User Plugin up to 1.0.1 on WordPress handle_return_to_admin authorization

Summaryinfo

A vulnerability was found in royalnavneet Login as User Plugin up to 1.0.1 on WordPress and classified as critical. Affected by this vulnerability is the function handle_return_to_admin. Executing a manipulation can lead to authorization. This vulnerability is handled as CVE-2026-5617. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in royalnavneet Login as User Plugin up to 1.0.1 on WordPress. It has been declared as critical. This vulnerability affects the function handle_return_to_admin. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The weakness was released by Ha Gia Bao. The advisory is shared for download at wordfence.com. This vulnerability was named CVE-2026-5617 since 04/05/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/15/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-22844). Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• royalnavneet

Name

• Login as User Plugin

Version

• 1.0.0
• 1.0.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion