Skip to main content

 Security

Security guidance and advisories for PageSeeder

CVE-2026-47759

TinyMCE: Unsafe restoration of internal URL and style attributes

Published2026-05-28
Last updated2026-11-16
ComponentTinyMCE
SeverityHigh
PageSeeder statusFixed

Summary

Forged data-mce-href, data-mce-src and data-mce-style attributes can override otherwise safe attributes during TinyMCE serialization, allowing cross-site scripting.

PageSeeder versions 6.0000 through 6.3003 inclusive are affected. The vulnerability is fixed in PageSeeder 6.3004 by an application-level parser fix in all three default TinyMCE editors. The bundled TinyMCE version remains 6.8.6; upstream component fixes are available in TinyMCE 7.9.3 and 8.5.1.

The upstream High classification (CVSS 3.1: 8.7) describes the component vulnerability; PageSeeder exposure is assessed separately.

For technical details, see the upstream security advisory .

PageSeeder impact assessment

Affected dependencyTinyMCE 6.8.6; application-level fix included in PageSeeder 6.3004
PageSeeder versions assessedAffected: PageSeeder 6.0000–6.3003 inclusive. Fixed: PageSeeder 6.3004.
Vulnerability statusFixed
Conditions required for exploitationAttacker-controlled HTML must carry forged internal TinyMCE attributes into an editor, and the restored values must subsequently reach a browser-rendered context.
Relevant PageSeeder configurationAll three default TinyMCE editors register a PreInit parser filter that strips incoming data-mce-href, data-mce-src and data-mce-style attributes. Server-side sanitization protects the reviewed comment/workflow and PSML HTML storage routes.
Assessment date2026-11-13

Assessment

PageSeeder 6.3004 fixes this issue in the PSML editor, form editor and property markup editor. The parser filter covers content set or inserted into an editor, including the PSML source-editing route.

Six tests using the real TinyMCE 6.8.6 editor reproduce the unfiltered vulnerability and verify the filter for the tested setContent and insertContent cases, preservation of normal content and undo. The rebuilt frontend bundles include the filter.

The filter removes incoming internal attributes while allowing TinyMCE to maintain the values needed for its live editing view. Undo/redo raw restoration bypasses the parser; the regression test explicitly verifies undo.

Before this fix, the reviewed comment and workflow HTML storage routes already used the OWASP-based server sanitizer. A stored-XSS bypass of those controls was not demonstrated. The affected-version classification concerns the vulnerable editor behavior and does not imply that every storage route was exploitable. Version-only scanners can continue to flag TinyMCE 6.8.6 despite the PageSeeder application-level fix.

The affected range, PageSeeder 6.0000 through 6.3003 inclusive, reflects reproduced unsafe serialization on each distinct shipped 6.0xxx and 6.1xxx TinyMCE build, as referenced in the TinyMCE advisory . The fix was verified in the reviewed PageSeeder 6.3004 source 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 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

Upgrade to PageSeeder 6.3004 or a later release

Administrators running PageSeeder 6.0000 through 6.3003 should upgrade to PageSeeder 6.3004 or a later release incorporating this fix. Deploy the matching frontend assets so that all three default editors receive the parser fix.

References

Created on , last edited on