CVE-2024-47875
DOMPurify: Nesting-based mutation cross-site scripting
| Published | 2024-10-11 |
|---|---|
| Last updated | 2026-11-16 |
| Component | DOMPurify |
| Severity | Critical |
| PageSeeder status | Not affected |
Summary
Crafted nested markup can cause a mutation-XSS sanitization bypass in affected DOMPurify versions.
The issue is fixed in DOMPurify 2.5.0 on the 2.x branch and 3.1.3 on the 3.x branch. PageSeeder includes 3.4.17 directly and 3.1.7 inside TinyMCE.
The upstream repository advisory labels this issue Critical. This upstream classification is distinct from PageSeeder exposure.
For technical details, see the upstream security advisory .
PageSeeder impact assessment
| Affected dependency | DOMPurify 3.4.17; embedded DOMPurify 3.1.7 |
|---|---|
| PageSeeder versions assessed | 6.0000–6.1006 (affected embedded DOMPurify copy), 6.2000–6.3004 (fixed embedded copy) |
| Vulnerability status | Not affected |
| Conditions required for exploitation | Attacker-controlled nested markup must be processed by an affected DOMPurify version and the result must reach a browser-rendered context. |
| Relevant PageSeeder configuration | Both identified DOMPurify versions, 3.4.17 and 3.1.7, are newer than the 3.x fix at 3.1.3. |
| Assessment date | 2026-11-13 |
Assessment
PageSeeder 6.3004 is not affected because every identified DOMPurify copy includes the fix for this CVE. A PageSeeder exploit was not demonstrated.
The older copy embedded in TinyMCE was assessed separately from the main npm dependency; checking only the main package would not establish this result.
This assessment applies to PageSeeder 6.3004 in the reviewed standard configuration and matching frontend assets. Custom templates, independently replaced components and additional editor integrations may change exposure. Historical releases 6.0000–6.3004 were tested; earlier versions were not independently assessed.
Evidence is based on source and shipped-asset review at repository on 13 November 2026, with targeted jsdom tests where described. It does not establish the configuration of every deployed server or demonstrate a real-browser exploit.
Recommended action
PageSeeder 6.0000–6.1006: Upgrade recommended
While a PageSeeder exploit was not demonstrated, these releases include an affected DOMPurify copy embedded in TinyMCE. Upgrade to PageSeeder 6.2000 or later to resolve this dependency.
PageSeeder 6.2000 and later: No action required
No CVE-specific action is required for installations using the assessed dependencies.