Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious clipboard HTML with slice-context attributes
-
DeliveryLure victim to paste into ProseMirror editor
-
ExploitUnvalidated context attributes bypass schema validation
-
ExecutionExecute arbitrary JavaScript in browser context
-
ImpactHijack session or exfiltrate user data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The application must embed prosemirror-view at a version prior to 1.42.3 as its editing surface, and a user must paste attacker-crafted HTML (containing slice-context attributes that are not run through schema attribute validation) into that editor. The decisive limiting factor is this required user interaction (CVSS UI:A): exploitation cannot occur without a victim performing a paste into the vulnerable editor, so it is not remotely triggerable without user action. Additional limits: only versions below 1.42.3 are affected, and the attacker must get their crafted content in front of a user likely to paste it into a ProseMirror-backed field. |
| Impact | This is a genuine, non-trivial client-side XSS (CWE-79) in a very widely-embedded editor library, but its real-world risk is moderated by a mandatory user-interaction gate. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:A, VC:H/VI:H) correctly flags network reachability, low complexity, and no privileges, but UI:A is the decisive limiter: exploitation requires the victim to actively paste attacker-crafted HTML into a ProseMirror-based editor - it is not a drive-by or server-side flaw. No EPSS score, KEV entry, or public PoC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the only exploitation signal is the fix commit itself (credited to researcher Pedro Paniago). The high confidentiality/integrity impact is justified because successful exploitation runs attacker-controlled JavaScript in the page hosting the editor, enabling session theft or actions-as-user. Net: a legitimately high-severity library bug that is a real patch priority for anyone embedding prosemirror-view, but not an emergency mass-exploitation threat given the paste-based interaction requirement and absence of KEV/PoC/EPSS signals. No conflicting signals were detected in the provided data, though the absence of EPSS and PoC status means spread/weaponization cannot be assessed. |
| Exploit ScenarioDerived | An attacker places specially crafted HTML on a page or in content a victim is likely to copy, then convinces the victim to paste it into a web application that embeds a ProseMirror editor prior to 1.42.3. During paste handling the clipboard slice context carries attributes that bypass schema attribute validation, and the resulting content executes attacker-controlled JavaScript in the victim's browser session. No public exploit was provided in the input, so this scenario is inferred from the description and the fix commit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Cross-site scripting in prosemirror-view (all versions prior to 1.42.3) lets unauthenticated attackers execute arbitrary JavaScript in the browser window hosting an editor when a victim pastes attacker-crafted HTML into a ProseMirror-backed field. The root cause is in the paste path: attributes delivered through the clipboard slice context are applied without being run through the schema's attribute validators, so crafted markup can smuggle content that the schema would normally reject. Exploitation is gated by that mandatory paste action (CVSS UI:A / UI:R), so it is not triggerable without victim interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis; the fix ships in 1.42.3 as a small change that runs attribute validators on slice-context attributes.
RemediationAI
Vendor-released patch: 1.42.3 - upgrade prosemirror-view to 1.42.3 or later (npm update prosemirror-view@^1.42.3) and regenerate lockfiles and any vendored bundles, since the flaw is fixed solely by running schema attribute validators on slice-context attributes from clipboard content; the release also contains small unrelated fixes for contenteditable widgets and trusted-type paste handling. If immediate upgrade is impossible, compensating controls in rough order of effectiveness and trade-off: sanitize or reject untrusted HTML before it reaches the editor (e.g., filter pasted markup through a strict allowlist sanitizer, dropping event-handler and URI attributes) - effective but can break legitimate rich paste from Office/Google Docs formats; intercept the paste pipeline using ProseMirror's transformPasted / handlePaste hooks to strip unknown slice-context attributes - narrower than sanitization but requires custom code and maintenance; disable HTML paste entirely and accept only plain text - strongly mitigates this class of paste-based DOM XSS at a significant usability cost; and enforce a Content-Security-Policy without 'unsafe-inline' for scripts, plus Trusted Types, to reduce the payload's reach - defense in depth only, not a substitute for patching, and requires the host application to adopt Trusted Types-aware rendering. Note that only versions below 1.42.3 are affected and no public exploit code or confirmed active exploitation was identified, so remediation should be prioritized by whether the application exposes an editor to untrusted paste input rather than treated as an emergency.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ProseMirror is a document-model toolkit in which a schema defines node types, marks, and their attributes; each attribute carries validate/parseDOM/toDOM behavior that constrains what content can exist in a document. The prosemirror-view package implements the browser-facing editable surface (contenteditable-based) and the clipboard/paste pipeline: when a user pastes HTML, the view parses the clipboard payload into a slice whose context attributes are used to reconstruct surrounding or wrapping content. In vulnerable versions, those slice context attributes were trusted and attached directly rather than passed through the schema attribute validators, so an attacker who controls the pasted HTML can inject attribute values the schema would have rejected - the classic XSS pivots being inline event handlers or URI-bearing attributes evaluated in the editor's page. This is CWE-79 (improper neutralization of input during web page generation), a DOM-based client-side variant operating through the clipboard rather than a server-rendered response, which is why the assessed vector is AV:N/AC:L/PR:N with UI:R and scope change (S:C), reflecting attacker code running in the hosting page's origin with high confidentiality and integrity impact but no availability impact. The CPE cpe:2.3:a:prosemirror:prosemirror-view:*:*:*:*:*:*:*:* describes the affected package generically, with all releases below 1.42.3 being in scope; version 1.42.3 (released 2026-08-25) is the first fixed release and also addresses two unrelated regressions noted in its changelog.
Know when Prosemirror View gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Network-delivered content with low complexity and no privileges, but the victim must paste (UI:R); XSS escapes the editor into the page (S:C) and runs arbitrary JavaScript enabling high C/I impact, no availability effect.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
ProseMirror's view component renders and manages the editable browser interface for ProseMirror documents. Prior to 1.42.3, prosemirror-view paste handling accepts attacker-provided HTML whose clipboard slice context contains attributes that are not passed through schema attribute validation. When a user pastes the crafted HTML into an editor, the unvalidated context attributes can construct content that executes attacker-controlled JavaScript in the browser window containing the editor. This issue is fixed in version 1.42.3.
Blast Radius
ecosystem impact- 27 npm packages depend on prosemirror-view (16 direct, 11 indirect)
Ecosystem-wide dependent count for version 1.42.3.
Technical POC Analysis
Evidence basis note: the only artifact supplied is advisory GHSA-c8x8-7fp4-3x9w (prosemirror-view, CVE-2026-104847, published 2026-08-25, credited to dropn0w).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
A cross-site scripting flaw in the ProseMirror-view rich-text editing component (all versions before 1.42.3) lets attacker-crafted HTML pasted from another page execute arbitrary JavaScript inside the browser session of anyone using an affected editor. Because ProseMirror is embedded in many third-party and internally built SaaS tools, exposure is spread across the application estate rather than confined to a single named product, and it depends on which of those tools accept pasted rich content. Successful exploitation could let an attacker act as the signed-in user - reading or exfiltrating data visible in that application, altering records, or pivoting into connected systems.
No vendor patch confirmed by the advisory (the description references a fix in prosemirror-view 1.42.3, which should be validated with the maintainers before relying on it); interim mitigations include sanitizing clipboard-sourced HTML server-side or on paste instead of trusting slice-context attributes, disabling rich-HTML paste in high-value editors, enforcing a strict Content Security Policy against inline and untrusted scripts, scoping editor sessions with least privilege and short session lifetimes, and prioritizing upgrades to 1.42.3 or later in any application that displays sensitive data.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-91749
GHSA-c8x8-7fp4-3x9w
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB