# GHSA-7jfh-2xc9-ccv7: Cross-Site Scripting in public

> Stored cross-site scripting vulnerability in the public npm module allows attackers to inject malicious scripts, with no current fix available.

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

## What is GHSA-7jfh-2xc9-ccv7?

GHSA-7jfh-2xc9-ccv7 is a cross-site scripting vulnerability in public, published on 31 May 2019. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

All versions of `public` are vulnerable to stored cross-site scripting (XSS). 

## Recommendation

No fix is currently available for this vulnerability. It is our recommendation to not install or use this module at this time.

## Which versions are affected by GHSA-7jfh-2xc9-ccv7?

4 open source packages ship an affected version, including public.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `public` | npm | All versions | None |
| `public` | npm | All versions | None |
| `public` | npm | All versions | 0.1.4 |
| `public` | npm | All versions | 0.1.4 |

## How do I fix GHSA-7jfh-2xc9-ccv7?

Upgrade public to 0.1.4 or later.

## Is GHSA-7jfh-2xc9-ccv7 being exploited?

There is no known exploitation of GHSA-7jfh-2xc9-ccv7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-7jfh-2xc9-ccv7 and fix it if it is affected.

What it is: GHSA-7jfh-2xc9-ccv7 is a cross-site scripting vulnerability in public, published on 31 May 2019. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-7jfh-2xc9-ccv7 in the wild and no public exploit code.

Affected packages and fixed versions:
- public (npm): affected all versions; no fix listed
- public (npm): affected all versions; no fix listed
- public (npm): affected all versions; fixed in 0.1.4
- public (npm): affected all versions; fixed in 0.1.4

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-7jfh-2xc9-ccv7/ (Markdown: https://insights.sbomify.com/GHSA-7jfh-2xc9-ccv7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-7jfh-2xc9-ccv7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-7jfh-2xc9-ccv7/
Summaries are generated and may contain mistakes; the official description above is the record.