How severe is GHSA-h6p3-p4vx-wr8q?

No CVSS score has been assigned to GHSA-h6p3-p4vx-wr8q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h6p3-p4vx-wr8q?

GHSA-h6p3-p4vx-wr8q affects the following packages: dompurify (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-h6p3-p4vx-wr8q?

Update dompurify to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6p3-p4vx-wr8q is resolved across your whole dependency graph.

How do I detect GHSA-h6p3-p4vx-wr8q in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-h6p3-p4vx-wr8q if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-h6p3-p4vx-wr8q actively exploited in the wild?

No public exploit code has been indexed for GHSA-h6p3-p4vx-wr8q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h6p3-p4vx-wr8q published, and has it been updated?

GHSA-h6p3-p4vx-wr8q was published on January 11, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

dompurify vulnerable to Cross-site ScriptingGHSA-h6p3-p4vx-wr8q

GHSA-h6p3-p4vx-wr8q is a security vulnerability in dompurify. A fix is available for dompurify — see the affected versions and patch details below.

Published

Jan 11, 2023

Updated

Jan 11, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jan 11, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍dompurify

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`dompurify`	all versions	2.2.3`pip install --upgrade 'dompurify==2.2.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dompurify to 2.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h6p3-p4vx-wr8q is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

dompurify prior to version 2.2.3 is vulnerable to a cross-site scripting problem caused by nested headlines.

O3 Security · Impact-Aware SCA

Is GHSA-h6p3-p4vx-wr8q in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works