How severe is GHSA-mjjq-c88q-qhr6?

No CVSS score has been assigned to GHSA-mjjq-c88q-qhr6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mjjq-c88q-qhr6?

GHSA-mjjq-c88q-qhr6 affects the following packages: dompurify (npm). Ecosystems affected: npm.

How do I fix GHSA-mjjq-c88q-qhr6?

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

How do I detect GHSA-mjjq-c88q-qhr6 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-mjjq-c88q-qhr6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mjjq-c88q-qhr6?

O3 pinpoints whether GHSA-mjjq-c88q-qhr6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-mjjq-c88q-qhr6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mjjq-c88q-qhr6 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-mjjq-c88q-qhr6 published, and has it been updated?

GHSA-mjjq-c88q-qhr6 was published on September 3, 2020 and was last updated on September 29, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-mjjq-c88q-qhr6

GHSA-mjjq-c88q-qhr6 is a security vulnerability in dompurify. O3 Security confirms whether GHSA-mjjq-c88q-qhr6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in dompurify

Published

Sep 3, 2020

Updated

Sep 29, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

dompurifynpm

62.7Mdownloads / week

Description

Versions of dompurify prior to 2.0.7 are vulnerable to Cross-Site Scripting (XSS). It is possible to bypass the package sanitization through Mutation XSS, which may allow an attacker to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 2.0.7 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dompurify`	all versions	2.0.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update dompurify to 2.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjjq-c88q-qhr6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-mjjq-c88q-qhr6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mjjq-c88q-qhr6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions of `dompurify` prior to 2.0.7 are vulnerable to Cross-Site Scripting (XSS). It is possible to bypass the package sanitization through Mutation XSS, which may allow an attacker to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 2.0.7 or later.

O3 Security · Impact-Aware SCA

Is GHSA-mjjq-c88q-qhr6 in your dependencies?

O3 detects GHSA-mjjq-c88q-qhr6 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works