CVE-2026-116803
DOMPurify: Detached-subtree bypass during in-place sanitization
| Published | 2026-10-26 |
|---|---|
| Last updated | 2026-11-16 |
| Component | DOMPurify |
| Severity | High |
| PageSeeder status | Not affected |
Summary
During in-place sanitization, a custom hook that detaches a parent or sibling can leave an unvisited subtree with executable event-handler attributes.
The GitHub-reviewed advisory lists DOMPurify through 3.4.16 as affected and 3.4.17 as fixed. PageSeeder includes a fixed main copy at 3.4.17 and older embedded copies at 3.1.7 in TinyMCE core and its silver theme.
Severity differs by source: the GitHub-reviewed/npm advisory is High, while the upstream repository advisory labels the issue Low. The High classification is retained here for vulnerability triage; it does not establish PageSeeder exploitability.
For technical details, see the upstream security advisory .
PageSeeder impact assessment
| Affected dependency | DOMPurify 3.1.7 embedded in TinyMCE; main DOMPurify 3.4.17 is fixed |
|---|---|
| PageSeeder versions assessed | PageSeeder 6.0000 through 6.3004 |
| Vulnerability status | Not affected |
| Conditions required for exploitation | An affected DOMPurify copy must sanitize in `IN_PLACE` mode, with a custom hook detaching a parent or an unvisited sibling such that executable content is not neutralized. |
| Relevant PageSeeder configuration | The main PageSeeder DOMPurify copy is 3.4.17. TinyMCE embeds 3.1.7, but its core parses editor input into a separate DOMParser document before in-place sanitization, and transfers only retained nodes to editor content. Its silver theme sanitizes strings without `IN_PLACE`. |
| Assessment date | 2026-11-13 |
Assessment
PageSeeder 6.3004 is not affected in the reviewed standard configuration. The main DOMPurify copy contains the fix. TinyMCE core uses an older copy, but its input parser sanitizes a separate DOMParser document and transfers only retained nodes into the editor. The silver theme calls its embedded sanitizer on strings without IN_PLACE.
An isolated test of the actual TinyMCE 6.8.6 parser showed that its data-mce-bogus removal hook can detach an image while its onerror attribute remains. The returned content omitted that subtree. In Brave, the same editor input did not execute the event handler; a control image created in the live page fired its handler after removal. This supports the distinction between TinyMCE's parsed document and the live-DOM condition required by the advisory. No PageSeeder exploit was reproduced.
Updating the top-level npm dependency does not replace a DOMPurify implementation embedded inside TinyMCE core or theme files.
This assessment applies to PageSeeder 6.0000 through 6.3004 in the reviewed standard configuration and matching frontend assets. Custom templates, independently replaced components and additional editor integrations may change exposure. The jsdom probes covered distinct historical TinyMCE builds across the assessed PageSeeder versions; the Brave probe covered the current build.
Evidence is based on source and shipped-asset review and targeted jsdom and Brave browser probes conducted on 13 November 2026 across PageSeeder versions 6.0000 to 6.3004.
Recommended action
No action required
In 6.3004, the main copy is fixed; historical releases contain older copies.
This assessment does not claim that TinyMCE's embedded DOMPurify version contains the upstream fix; it establishes that the reviewed standard PageSeeder paths do not meet this CVE's live-DOM exploit conditions.
References
- CVE-2026-116803 record
- Upstream security advisory
- DOMPurify upstream advisory and severity classification