CVE-2023-51484

Login as User or Customer (User Switching) <= 3.8 - Authentication Bypass

2023-12-27 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 3.9.1
Affected Version
<= 3.8
CVSS
9.8Critical
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2023-51484
View all Login as User or Customer — User Switching vulnerabilities

At a glance

CVE-2023-51484 is a critical-severity Improper Authentication vulnerability in the Login as User or Customer WordPress plugin, affecting versions <= 3.8. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.9.1; sites on affected versions should update now. Disclosed December 2023, reported by Rafie Muhammad.

Vulnerability Overview

The Login as User or Customer plugin for WordPress is vulnerable to authentication bypass in all versions up to, and including, 3.8. This makes it possible for unauthenticated attackers to login as another user and escalate their privileges.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-287: Improper Authentication

Reaching this weakness in Login as User or Customer <= 3.8 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Login as User or Customer the fix is 3.9.1: builds <= 3.8 are affected, anything from 3.9.1 onward is not.

Remediation

Update to version 3.9.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Login as User or Customer 3.9.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C