# GHSA-pgjv-jrg2-gq3v: dompurify vulnerable to Cross-site Scripting

> An attacker can execute arbitrary scripts in a victim's browser via crafted SVG content processed by the library.

- **Severity:** Not scored
- **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:** 11 Jan 2023

## What is GHSA-pgjv-jrg2-gq3v?

GHSA-pgjv-jrg2-gq3v is a cross-site scripting vulnerability in dompurify, published on 11 Jan 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

dompurify prior to version 2.2.2 is vulnerable to cross-site scripting when converting from SVG namespace.

## Which versions are affected by GHSA-pgjv-jrg2-gq3v?

2 open source packages ship an affected version, including dompurify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dompurify` | PyPI | All versions | 2.2.2 |
| `dompurify` | PyPI | All versions | 2.2.2 |

## How do I fix GHSA-pgjv-jrg2-gq3v?

Upgrade dompurify to 2.2.2 or later.

## Is GHSA-pgjv-jrg2-gq3v being exploited?

There is no known exploitation of GHSA-pgjv-jrg2-gq3v in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-pgjv-jrg2-gq3v and fix it if it is affected.

What it is: GHSA-pgjv-jrg2-gq3v is a cross-site scripting vulnerability in dompurify, published on 11 Jan 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 GHSA-pgjv-jrg2-gq3v in the wild and no public exploit code.

Affected packages and fixed versions:
- dompurify (PyPI): affected all versions; fixed in 2.2.2
- dompurify (PyPI): affected all versions; fixed in 2.2.2

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/GHSA-pgjv-jrg2-gq3v/ (Markdown: https://insights.sbomify.com/GHSA-pgjv-jrg2-gq3v/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-pgjv-jrg2-gq3v

---
From sbomify Insights: https://insights.sbomify.com/GHSA-pgjv-jrg2-gq3v/
Summaries are generated and may contain mistakes; the official description above is the record.