How severe is GHSA-g9wg-wq4f-2x5w?

No CVSS score has been assigned to GHSA-g9wg-wq4f-2x5w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g9wg-wq4f-2x5w?

GHSA-g9wg-wq4f-2x5w affects the following packages: console-feed (npm). Ecosystems affected: npm.

How do I fix GHSA-g9wg-wq4f-2x5w?

Update console-feed to 2.8.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9wg-wq4f-2x5w is resolved across your whole dependency graph.

How do I detect GHSA-g9wg-wq4f-2x5w in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for console-feed. 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-g9wg-wq4f-2x5w 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-g9wg-wq4f-2x5w?

O3 pinpoints whether GHSA-g9wg-wq4f-2x5w 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-g9wg-wq4f-2x5w actively exploited in the wild?

No public exploit code has been indexed for GHSA-g9wg-wq4f-2x5w 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-g9wg-wq4f-2x5w published, and has it been updated?

GHSA-g9wg-wq4f-2x5w was published on September 3, 2020 and was last updated on August 31, 2020. 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-g9wg-wq4f-2x5w

GHSA-g9wg-wq4f-2x5w is a security vulnerability in console-feed. O3 Security confirms whether GHSA-g9wg-wq4f-2x5w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-Site Scripting in console-feed

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦console-feed

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 console-feed prior to 2.8.10 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape the rendered output. If an application uses console-feed and a malicious JavaScript payload was passed to a console.log('%_', payload) call, the package would render HTML containing the malicious payload.

Recommendation

Upgrade to version 2.8.10 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`console-feed`	all versions	2.8.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for console-feed. 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 console-feed to 2.8.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9wg-wq4f-2x5w 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-g9wg-wq4f-2x5w 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-g9wg-wq4f-2x5w. 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 `console-feed` prior to 2.8.10 are vulnerable to Cross-Site Scripting (XSS). The package fails to properly escape the rendered output. If an application uses `console-feed` and a malicious JavaScript payload was passed to a `console.log('%_', payload)` call, the package would render HTML containing the malicious payload. ## Recommendation Upgrade to version 2.8.10 or later.

O3 Security · Impact-Aware SCA

Is GHSA-g9wg-wq4f-2x5w in your dependencies?

O3 detects GHSA-g9wg-wq4f-2x5w 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