# CVE-2025-3191: React Draft Wysiwyg Cross-Site Scripting (XSS) via the Embedded Button

> Attackers can inject malicious scripts via the Embedded button in react-draft-wysiwyg, leading to Cross-site Scripting attacks.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N/E:P`)
- **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:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-fq5x-7292-2p5r

## What is CVE-2025-3191?

CVE-2025-3191 is a medium-severity cross-site scripting vulnerability in react-draft-wysiwyg, published on 4 Apr 2025. 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

All versions of the package react-draft-wysiwyg are vulnerable to Cross-site Scripting (XSS) via the Embedded button which will then result in saving the payload in the <iframe> tag.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-3191?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `react-draft-wysiwyg` | npm | All versions to 1.15.0 | None |
| `react-draft-wysiwyg` | npm | All versions to 1.15.0 | None |

## How do I fix CVE-2025-3191?

No fix has been published for CVE-2025-3191 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3191 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3191 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3191 and fix it if it is affected.

What it is: CVE-2025-3191 is a medium-severity cross-site scripting vulnerability in react-draft-wysiwyg, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3191 exists.

Affected packages and fixed versions:
- react-draft-wysiwyg (npm): affected all versions up to 1.15.0; no fix listed
- react-draft-wysiwyg (npm): affected all versions up to 1.15.0; no fix listed

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/CVE-2025-3191/ (Markdown: https://insights.sbomify.com/CVE-2025-3191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3191
- OSV: https://osv.dev/vulnerability/CVE-2025-3191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3191/
Summaries are generated and may contain mistakes; the official description above is the record.