@webiny/react-rich-text-renderer vulnerable to insecure rendering of rich text contentGHSA-3x59-vrmc-5mx6
MEDIUMFix: webiny/webiny-js@8748bc5GHSA-3x59-vrmc-5mx6 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in @webiny/react-rich-text-renderer. A fix is available for @webiny/react-rich-text-renderer — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-3x59-vrmc-5mx6.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
@webiny/react-rich-text-renderernpmDescription
Overview
@webiny/react-rich-text-renderer is a react component to render data coming from Webiny Headless CMS and Webiny Form Builder. The @webiny/react-rich-text-renderer package depends on the editor.js rich text editor to handle rich text content. The CMS stores rich text content from the editor.js into the database. When the @webiny/react-rich-text-renderer is used to render such content, it uses the dangerouslySetInnerHTML prop, without applying HTML sanitization. The issue arises when an actor, who in this context would specifically be a content manager with access to the CMS, inserts a malicious script as part of the user-defined input. This script is then injected and executed within the user's browser when the main page or admin page loads.
Am I affected?
You will be affected if you're running a Webiny project created prior to 5.35.0 and you're using the legacy rich text editor (which uses editor.js library under the hood). If you've already switched to using the new rich text editor, powered by Lexical editor, you will not be affected by this.
How do I patch this vulnerability?
Update to Webiny version 5.37.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @webiny/react-rich-text-renderer | all versions | 5.37.2npm install @webiny/react-rich-text-renderer@5.37.2 |
Affected Products
webinywebinyDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @webiny/react-rich-text-renderer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @webiny/react-rich-text-renderer to 5.37.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3x59-vrmc-5mx6 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 GHSA-3x59-vrmc-5mx6 in your dependencies?
Find it across npm, including transitive dependencies.