# CVE-2024-51915: WordPress LiteSpeed Cache plugin <= 6.5.2 - Cross Site Scripting (XSS) vulnerability

> Attackers can inject malicious scripts into WordPress sites using the LiteSpeed Cache plugin, potentially compromising user sessions and site integrity.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-prpx-gw6q-vpv2

## What is CVE-2024-51915?

CVE-2024-51915 is a medium-severity cross-site scripting vulnerability in LiteSpeed Cache, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Stored XSS.This issue affects LiteSpeed Cache: from n/a through <= 6.5.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2024-51915 being exploited?

There is no known exploitation of CVE-2024-51915 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51915 is a medium-severity cross-site scripting vulnerability in LiteSpeed Cache, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-51915 in the wild and no public exploit code.

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-51915/ (Markdown: https://insights.sbomify.com/CVE-2024-51915/index.md)
```

## Sources

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

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