How severe is GHSA-hg79-j56m-fxgv?

No CVSS score has been assigned to GHSA-hg79-j56m-fxgv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hg79-j56m-fxgv?

GHSA-hg79-j56m-fxgv affects the following packages: react (npm). Ecosystems affected: npm.

How do I fix GHSA-hg79-j56m-fxgv?

Update react to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hg79-j56m-fxgv is resolved across your whole dependency graph.

How do I detect GHSA-hg79-j56m-fxgv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react. 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-hg79-j56m-fxgv 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-hg79-j56m-fxgv?

O3 pinpoints whether GHSA-hg79-j56m-fxgv 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-hg79-j56m-fxgv actively exploited in the wild?

No public exploit code has been indexed for GHSA-hg79-j56m-fxgv 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-hg79-j56m-fxgv published, and has it been updated?

GHSA-hg79-j56m-fxgv was published on September 4, 2020 and was last updated on October 1, 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-hg79-j56m-fxgv

GHSA-hg79-j56m-fxgv is a security vulnerability in react. O3 Security confirms whether GHSA-hg79-j56m-fxgv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in react

Published

Sep 4, 2020

Updated

Oct 1, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 1, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦react

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

Description

Versions of react prior to 0.14.0 are vulnerable to Cross-Site Scripting (XSS). The package's createElement function fails to properly validate its input object, allowing attackers to execute arbitrary JavaScript in a victim's browser.

Recommendation

Upgrade to version 0.14.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`react`	≥ 0.0.1&&< 0.14.0	0.14.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react. 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 react to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hg79-j56m-fxgv 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-hg79-j56m-fxgv 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-hg79-j56m-fxgv. 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 `react` prior to 0.14.0 are vulnerable to Cross-Site Scripting (XSS). The package's `createElement` function fails to properly validate its input object, allowing attackers to execute arbitrary JavaScript in a victim's browser. ## Recommendation Upgrade to version 0.14.0 or later.

O3 Security · Impact-Aware SCA

Is GHSA-hg79-j56m-fxgv in your dependencies?

O3 detects GHSA-hg79-j56m-fxgv 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