CVE-2024-28000

LiteSpeed Cache <= 6.3.0.1 - Unauthenticated Privilege Escalation

2024-08-21 00:00
John Blackbourn

Strategic Overview

Status
Patched in 6.4
Affected Plugin
LiteSpeed Cache
Affected Version
<= 6.3.0.1
CVSS
9.8Critical
Weakness type
CWE-269 · Improper Privilege Management
CVE
CVE-2024-28000
View all LiteSpeed Cache vulnerabilities

At a glance

CVE-2024-28000 is a critical-severity Improper Privilege Management vulnerability in the LiteSpeed Cache WordPress plugin, affecting versions <= 6.3.0.1. 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 6.4; sites on affected versions should update now. Disclosed August 2024, reported by John Blackbourn.

Vulnerability Overview

The LiteSpeed Cache plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 6.3.0.1. This is due to the plugin not properly restricting the role simulation functionality allowing a user to set their current ID to that of an administrator, if they have access to a valid hash which can be found in the debug logs or brute forced. This makes it possible for unauthenticated attackers to spoof their user ID to that of an administrator, and then create a new user account with the administrator role utilizing the /wp-json/wp/v2/users REST API endpoint. In some environments, the crawler may be disabled making this a non-exploitable issue in those instances.

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-269: Improper Privilege Management

Reaching this weakness in LiteSpeed Cache <= 6.3.0.1 takes no account at all. Improper privilege management means the code lets an account end up with capabilities its role should not have.

It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For LiteSpeed Cache the fix is 6.4: builds <= 6.3.0.1 are affected, anything from 6.4 onward is not.

Remediation

Update to version 6.4, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: LiteSpeed Cache 6.4 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