Cross-Site Scripting (XSS) in prosemirror-view (CVE-2026-104847)
Summary
Cross-site scripting in prosemirror-view (CVE-2026-104847). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.42.3 or later.
Original description
The description as published by the source.
Impact
When a user pastes attacker-provided HTML into a ProseMirror editor component, this can cause attacker-controlled JavaScript code to run in the browser window containing the editor.
Patches
Version 1.42.3 adds validation that prevents this attack.
Workarounds
No known workarounds.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-104847 has been found in prosemirror-view.
Risk of unauthorized operations or information disclosure.
What to do: upgrade prosemirror-view to 1.42.3 or later.
If unsure, ask your IT team or search "prosemirror-view CVE-2026-104847" on the vendor's site.
CVE-2026-104847 (prosemirror-view) — CWE-79
Patched: 1.42.3 — 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 prosemirror-view.
Check the vendor advisory for the affected versions of prosemirror-view.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.42.3.
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 'prosemirror-view' . 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 'prosemirror-view' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
prosemirror-viewを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade prosemirror-view to 1.42.3ステージング環境で 1.42.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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 github.com
- web github.com