# CVE-2022-48345: @braintree/sanitize-url Cross-site Scripting vulnerability

> An attacker can execute arbitrary scripts via HTML entities in URLs using the sanitize-url library, affecting applications relying on it for security.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-q8gg-vj6m-hgmj, UBUNTU-CVE-2022-48345

## What is CVE-2022-48345?

CVE-2022-48345 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

sanitize-url (aka @braintree/sanitize-url) before 6.0.2 allows XSS via HTML entities.

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

## Which versions are affected by CVE-2022-48345?

2 open source packages ship an affected version, including @braintree/sanitize-url. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@braintree/sanitize-url` | npm | All versions | 6.0.1 |
| `@braintree/sanitize-url` | npm | All versions | 6.0.1 |

Products: Paypal Braintree\/Sanitize-Url.

## How do I fix CVE-2022-48345?

Upgrade @braintree/sanitize-url to 6.0.1 or later.

## Is CVE-2022-48345 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48345 and fix it if it is affected.

What it is: CVE-2022-48345 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-48345 in the wild and no public exploit code.

Affected packages and fixed versions:
- @braintree/sanitize-url (npm): affected all versions; fixed in 6.0.1
- @braintree/sanitize-url (npm): affected all versions; fixed in 6.0.1

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

## Sources

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

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