Skip to main content

 Security

Security guidance and advisories for PageSeeder

CVE-2026-116804

DOMPurify: Template-expression bypass in attached shadow roots

Published2026-10-26
Last updated2026-11-13
ComponentDOMPurify
SeverityCritical
PageSeeder statusNot affected

Summary

With SAFE_FOR_TEMPLATES and a DOM-returning or in-place mode, split template expressions can survive sanitization inside an attached shadow root. A downstream template engine may evaluate the reconstructed expression.

The upstream affected range is 3.4.4 through 3.4.16. The issue is fixed in 3.4.17.

The upstream GitHub advisory classifies the issue Critical. This component severity is distinct from PageSeeder exposure.

For technical details, see the upstream security advisory .

PageSeeder impact assessment

Affected dependencyDOMPurify 3.4.17; embedded DOMPurify 3.1.7
PageSeeder versions assessedPageSeeder 6.0000 through 6.3004
Vulnerability statusNot affected
Conditions required for exploitationAn affected version must process an attacker-supplied DOM carrying a shadow root, with `SAFE_FOR_TEMPLATES` and a DOM output mode enabled, before a downstream template engine evaluates the surviving expression.
Relevant PageSeeder configurationThe main shipped DOMPurify is 3.4.17. TinyMCE embeds 3.1.7, which predates the published affected range. No PageSeeder `SAFE_FOR_TEMPLATES` configuration was found. Older releases (6.0000–6.3003) contain unfixed DOMPurify copies, but the reviewed standard editor parsing flow did not expose the required live-DOM condition.
Assessment date2026-11-13

Assessment

PageSeeder 6.3004 is not affected by the published version range. The main copy contains the fix and the identified embedded copies fall outside that range.

The additional configuration prerequisite was not found in PageSeeder application code. This conclusion does not imply that the embedded older copies are free of other vulnerabilities.

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.

Evidence is based on source and shipped-asset review 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

No action required

No CVE-specific action is required for installations matching the assessed dependency versions and configuration.

References

Created on , last edited on