# CVE-2025-48050: Path traversal in DOMPurify

> A path traversal vulnerability in DOMPurify's development server script allows reading files outside the working directory if manually started.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2025
- **Updated:** 16 May 2025
- **Also known as:** DEBIAN-CVE-2025-48050, GHSA-5h64-37wc-rj27, UBUNTU-CVE-2025-48050

## What is CVE-2025-48050?

CVE-2025-48050 is a high-severity path traversal vulnerability in Cure53 DOMPurify, published on 15 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In DOMPurify through 3.2.5 before 6bc6d60, scripts/server.js does not ensure that a pathname is located under the current working directory. NOTE: the Supplier disputes the significance of this report because the "Uncontrolled data used in path expression" occurs "in a development helper script which starts a local web server if needed and must be manually started."

Weakness: CWE-24 (Path Traversal: '../filedir')

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


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

Apply the vendor's patch.

## Is CVE-2025-48050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48050 is a high-severity path traversal vulnerability in Cure53 DOMPurify, published on 15 May 2025. 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-2025-48050 exists.

Affected product: Cure53 DOMPurify. 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-48050/ (Markdown: https://insights.sbomify.com/CVE-2025-48050/index.md)
```

## Sources

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

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