# GHSA-5g6j-8hv4-vfgj: Cross-Site Scripting in node-red

> Attackers can inject malicious scripts via unsanitized item names, leading to arbitrary JavaScript execution in victim browsers.

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

## What is GHSA-5g6j-8hv4-vfgj?

GHSA-5g6j-8hv4-vfgj is a cross-site scripting vulnerability in node-red, published on 11 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Versions of `node-red` prior to 0.18.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize the `name` field in new items, allowing attackers to execute arbitrary JavaScript in the victim's browser.

## Recommendation

Upgrade to version 0.18.6 or later.

## Which versions are affected by GHSA-5g6j-8hv4-vfgj?

2 open source packages ship an affected version, including node-red.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-red` | npm | All versions | 0.18.6 |
| `node-red` | npm | All versions | 0.18.6 |

## How do I fix GHSA-5g6j-8hv4-vfgj?

Upgrade node-red to 0.18.6 or later.

## Is GHSA-5g6j-8hv4-vfgj being exploited?

There is no known exploitation of GHSA-5g6j-8hv4-vfgj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-5g6j-8hv4-vfgj and fix it if it is affected.

What it is: GHSA-5g6j-8hv4-vfgj is a cross-site scripting vulnerability in node-red, published on 11 Sep 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-5g6j-8hv4-vfgj in the wild and no public exploit code.

Affected packages and fixed versions:
- node-red (npm): affected all versions; fixed in 0.18.6
- node-red (npm): affected all versions; fixed in 0.18.6

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-5g6j-8hv4-vfgj/ (Markdown: https://insights.sbomify.com/GHSA-5g6j-8hv4-vfgj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-5g6j-8hv4-vfgj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-5g6j-8hv4-vfgj/
Summaries are generated and may contain mistakes; the official description above is the record.