Cross-Site Scripting (XSS) in @webiny/react-rich-text-renderer (CVE-2023-41167)
Summary
Cross-site scripting in @webiny/react-rich-text-renderer (CVE-2023-41167). Risk of unauthorized operations or information disclosure. Exploitable via editor.js. Mitigation: upgrade to 5.37.2 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-41167 has been found in @webiny/react-rich-text-renderer.
Attackers can target a specific entry point like editor.js over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @webiny/react-rich-text-renderer to 5.37.2 or later.
If unsure, ask your IT team or search "@webiny/react-rich-text-renderer CVE-2023-41167" on the vendor's site.
CVE-2023-41167 (@webiny/react-rich-text-renderer) — CWE-79
Attack vector: remote (network-reachable)
Attack surface: editor.js / dangerouslySetInnerHTML
Patched: 5.37.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in @webiny/react-rich-text-renderer. Attackers reach the vulnerable code path via editor.js.
Check the vendor advisory for the affected versions of @webiny/react-rich-text-renderer. Attack surface: editor.js / dangerouslySetInnerHTML.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.37.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@webiny/react-rich-text-renderer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@webiny/react-rich-text-renderer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@webiny/react-rich-text-rendererを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @webiny/react-rich-text-renderer to 5.37.2ステージング環境で 5.37.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web webiny.com