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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g9wg-wq4f-2x5w 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-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

Cross-Site Scripting in console-feedGHSA-g9wg-wq4f-2x5w

GHSA-g9wg-wq4f-2x5w is a security vulnerability in console-feed. A fix is available for console-feed — see the affected versions and patch details below.

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

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.

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

console-feednpm

14Kdownloads / week

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`npm install console-feed@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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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

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?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works