# GHSA-g9wg-wq4f-2x5w: Cross-Site Scripting in console-feed

> Cross-Site Scripting in console-feed allows attackers to execute arbitrary JavaScript via malicious console.log payloads.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-g9wg-wq4f-2x5w?

GHSA-g9wg-wq4f-2x5w is a cross-site scripting vulnerability in console-feed, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

## Which versions are affected by GHSA-g9wg-wq4f-2x5w?

2 open source packages ship an affected version, including console-feed.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `console-feed` | npm | All versions | 2.8.10 |
| `console-feed` | npm | All versions | 2.8.10 |

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

Upgrade console-feed to 2.8.10 or later.

## Is GHSA-g9wg-wq4f-2x5w being exploited?

There is no known exploitation of GHSA-g9wg-wq4f-2x5w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g9wg-wq4f-2x5w and fix it if it is affected.

What it is: GHSA-g9wg-wq4f-2x5w is a cross-site scripting vulnerability in console-feed, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-g9wg-wq4f-2x5w in the wild and no public exploit code.

Affected packages and fixed versions:
- console-feed (npm): affected all versions; fixed in 2.8.10
- console-feed (npm): affected all versions; fixed in 2.8.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-g9wg-wq4f-2x5w/ (Markdown: https://insights.sbomify.com/GHSA-g9wg-wq4f-2x5w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g9wg-wq4f-2x5w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g9wg-wq4f-2x5w/
Summaries are generated and may contain mistakes; the official description above is the record.