How severe is GHSA-96g7-g7g9-jxw8?

No CVSS score has been assigned to GHSA-96g7-g7g9-jxw8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-96g7-g7g9-jxw8?

GHSA-96g7-g7g9-jxw8 affects the following packages: happy-dom (npm). Ecosystems affected: npm.

How do I fix GHSA-96g7-g7g9-jxw8?

Update happy-dom to 15.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-96g7-g7g9-jxw8 is resolved across your whole dependency graph.

How do I detect GHSA-96g7-g7g9-jxw8 in my npm dependencies?

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

How do I mitigate GHSA-96g7-g7g9-jxw8 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is GHSA-96g7-g7g9-jxw8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-96g7-g7g9-jxw8 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.

What is the EPSS score for GHSA-96g7-g7g9-jxw8?

GHSA-96g7-g7g9-jxw8 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-96g7-g7g9-jxw8?

GHSA-96g7-g7g9-jxw8 is classified as Cross-site Scripting (XSS) (CWE-79), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-96g7-g7g9-jxw8 published, and has it been updated?

GHSA-96g7-g7g9-jxw8 was published on November 6, 2024 and was last updated on November 6, 2024. 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

happy-dom allows for server side code to be executed by a <script> tagGHSA-96g7-g7g9-jxw8

Fix: capricorn86/happy-dom#1586

GHSA-96g7-g7g9-jxw8 is a Cross-site Scripting (XSS) vulnerability in happy-dom. A fix is available for happy-dom — see the affected versions and patch details below.

Also known asCVE-2024-51757

Published

Nov 6, 2024

Updated

Nov 6, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-96g7-g7g9-jxw8.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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.

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

happy-domnpm

33.3Mdownloads / week

Description

happy-dom is a JavaScript implementation of a web browser without its graphical user interface. Versions of happy-dom prior to 15.10.2 may execute code on the host via a script tag. This would execute code in the user context of happy-dom. Users are advised to upgrade to version 15.10.2. There are no known workarounds for this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`happy-dom`	all versions	15.10.2`npm install happy-dom@15.10.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for happy-dom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update happy-dom to 15.10.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-96g7-g7g9-jxw8 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### Impact Consumers of the NPM package `happy-dom` ### Patches The security vulnerability has been patched in v15.10.2 ### Workarounds No easy workarounds to my knowledge ### References [#1585](https://github.com/capricorn86/happy-dom/issues/1585)

O3 Security · Impact-Aware SCA

Is GHSA-96g7-g7g9-jxw8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works