# CVE-2025-47437: WordPress LiteSpeed Cache plugin <= 7.0.1 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery flaw in the LiteSpeed Cache plugin to make the server send requests to unintended locations.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-wj3g-88qg-cwfg

## What is CVE-2025-47437?

CVE-2025-47437 is a medium-severity server-side request forgery vulnerability in LiteSpeed Cache, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in LiteSpeed Technologies LiteSpeed Cache litespeed-cache.This issue affects LiteSpeed Cache: from n/a through <= 7.0.1.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-47437?


## How do I fix CVE-2025-47437?

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

## Is CVE-2025-47437 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47437 and fix it if it is affected.

What it is: CVE-2025-47437 is a medium-severity server-side request forgery vulnerability in LiteSpeed Cache, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-47437 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-2025-47437/ (Markdown: https://insights.sbomify.com/CVE-2025-47437/index.md)
```

## Sources

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

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