# GHSA-8xqr-4cpm-wx7g: Cross-Site Scripting in react-svg

> An attacker can execute arbitrary scripts via malicious SVG files rendered by the react-svg library, potentially compromising user sessions.

- **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:** 31 May 2019

## What is GHSA-8xqr-4cpm-wx7g?

GHSA-8xqr-4cpm-wx7g is a cross-site scripting vulnerability in react-svg, published on 31 May 2019. 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 `react-svg` before 2.2.18 are vulnerable to cross-site scripting (xss). This is due to the fact that scripts found in SVG files are run by default.

## Recommendation

Update to version 2.2.18 or later.

## Which versions are affected by GHSA-8xqr-4cpm-wx7g?

2 open source packages ship an affected version, including react-svg.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-svg` | npm | All versions | 2.2.18 |
| `react-svg` | npm | All versions | 2.2.18 |

## How do I fix GHSA-8xqr-4cpm-wx7g?

Upgrade react-svg to 2.2.18 or later.

## Is GHSA-8xqr-4cpm-wx7g being exploited?

There is no known exploitation of GHSA-8xqr-4cpm-wx7g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8xqr-4cpm-wx7g and fix it if it is affected.

What it is: GHSA-8xqr-4cpm-wx7g is a cross-site scripting vulnerability in react-svg, published on 31 May 2019. 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-8xqr-4cpm-wx7g in the wild and no public exploit code.

Affected packages and fixed versions:
- react-svg (npm): affected all versions; fixed in 2.2.18
- react-svg (npm): affected all versions; fixed in 2.2.18

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-8xqr-4cpm-wx7g/ (Markdown: https://insights.sbomify.com/GHSA-8xqr-4cpm-wx7g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8xqr-4cpm-wx7g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8xqr-4cpm-wx7g/
Summaries are generated and may contain mistakes; the official description above is the record.