CVE-2021-31712 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in react-draft-wysiwyg. 1 public exploit reference exists, so weaponization risk is real. A fix is available for react-draft-wysiwyg — see the affected versions and patch details below.
Cross-site Scripting in React Draft Wysiwyg
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-31712 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
react-draft-wysiwygnpmDescription
react-draft-wysiwyg (aka React Draft Wysiwyg) before 1.14.6 allows a javascript: URi in a Link Target of the link decorator in decorators/Link/index.js when a draft is shared across users, leading to XSS.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | react-draft-wysiwyg | all versions | 1.14.6npm install react-draft-wysiwyg@1.14.6 |
Affected Products
react draft wysiwygreact_draft_wysiwyg_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for react-draft-wysiwyg, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update react-draft-wysiwyg to 1.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-31712 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2021-31712 in your dependencies?
Find it across npm, including transitive dependencies.