# CVE-2024-28000: WordPress LiteSpeed Cache plugin <= 6.3.0.1 - Unauthenticated Privilege Escalation vulnerability

> Unauthenticated attackers can escalate privileges in the LiteSpeed Cache WordPress plugin due to incorrect privilege assignment.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2024
- **Updated:** 29 Apr 2026
- **Also known as:** GHSA-3cp9-7899-h8r7

## What is CVE-2024-28000?

CVE-2024-28000 is a critical vulnerability in LiteSpeed Cache, published on 21 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Privilege Assignment vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache.This issue affects LiteSpeed Cache: from n/a through <= 6.3.0.1.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2024-28000?

It affects 1 product.


Products: Litespeedtech Litespeed Cache.

## How do I fix CVE-2024-28000?

No fix has been published for CVE-2024-28000 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-28000 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28000 exists.

Public exploit code:

- LiteSpeed Cache Privilege Escalation PoC (github_poc): https://github.com/Alucard0x1/CVE-2024-28000
- PoC for the CVE-2024 Litespeed Cache Privilege Escalation  (github_poc): https://github.com/arch1m3d/CVE-2024-28000
- CVE-2024-28000 Exploit for litespeed-cache =<6.3 allows Privilege Escalation with creation of administrator account (github_poc): https://github.com/JohnDoeAnonITA/CVE-2024-28000
- CVE-2024-28000 LiteSpeed Cache Privilege Escalation Scan&Exp (github_poc): https://github.com/SSSSuperX/CVE-2024-28000
- Litespeed Cache WordPress Plugin 6.3.0.1 - Privilege Escalation (exploitdb)
- Hands-on exploit lab for CVE-2024-28000 — unauthenticated privilege escalation in LiteSpeed Cache (WordPress plugin, <=6.3.0.1). Spins up a vulnerable environment with Docker and includes a Go-based brute-forcer that cracks the weak mt_rand hash to create an administrator account. (github_poc): https://github.com/AliHzSec/CVE-2024-28000

## Other vulnerabilities in LiteSpeed Cache

- [CVE-2024-44000](https://insights.sbomify.com/CVE-2024-44000/): WordPress LiteSpeed Cache plugin < 6.5.0.1 - Unauthenticated Account Takeover via Cookie Leak vulnerability (critical 9.8)
- [CVE-2024-47637](https://insights.sbomify.com/CVE-2024-47637/): WordPress LiteSpeed Cache plugin <= 6.4.1 - Path Traversal vulnerability (high 8.8)
- [CVE-2023-40000](https://insights.sbomify.com/CVE-2023-40000/): WordPress LiteSpeed Cache plugin <= 5.7 - Unauthenticated Site Wide Stored XSS vulnerability (high 8.3)
- [CVE-2023-45000](https://insights.sbomify.com/CVE-2023-45000/): WordPress LiteSpeed Cache plugin <= 5.7 - Unauthenticated Broken Access Control on API vulnerability (high 8.2)
- [CVE-2024-50550](https://insights.sbomify.com/CVE-2024-50550/): WordPress LiteSpeed Cache plugin <= 6.5.1 - Privilege Escalation vulnerability (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28000 and fix it if it is affected.

What it is: CVE-2024-28000 is a critical vulnerability in LiteSpeed Cache, published on 21 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28000 exists.

Affected product: LiteSpeed Cache. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-28000/ (Markdown: https://insights.sbomify.com/CVE-2024-28000/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-28000
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-28000
- OSV: https://osv.dev/vulnerability/CVE-2024-28000

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-28000/
Summaries are generated and may contain mistakes; the official description above is the record.