CVE-2026-47760
TinyMCE: Nested SVG namespace sanitization bypass
| Published | 2026-05-28 |
|---|---|
| Last updated | 2026-11-16 |
| Component | TinyMCE |
| Severity | High |
| PageSeeder status | Fixed |
Summary
Improper SVG namespace handling can allow crafted nested elements to bypass TinyMCE attribute sanitization and introduce executable markup.
The vulnerability affects TinyMCE 6.8.0 through versions before 7.1.0. The bundled version, 6.8.6, is within this range. The issue is fixed upstream in 7.1.0.
The upstream High classification is CVSS 3.1: 8.7. No cross-user stored-XSS exploit was demonstrated in the reviewed PageSeeder flows.
For technical details, see the upstream security advisory .
PageSeeder impact assessment
| Affected dependency | TinyMCE 6.8.6 |
|---|---|
| PageSeeder versions assessed | Shipped TinyMCE is outside the published affected range through 6.0014; 6.1000–6.3003 ship affected editor assets; 6.3004 includes the backported fix. Shipped versions inspected; the original and patched 6.8.6 assets tested. |
| Vulnerability status | Fixed |
| Conditions required for exploitation | In an unpatched TinyMCE 6.8.6 editor, crafted nested SVG before an iframe can leave the SVG namespace tracker in the wrong state and retain an attribute normally removed by the editor. This was reproduced with a restrictive TinyMCE schema. The current local build corrects the tracker. |
| Relevant PageSeeder configuration | The PSML editor accepts source input and uses valid_elements: *[*]. The current build backports the namespace fix into its bundled TinyMCE 6.8.6 asset and enables sandbox_iframes for a separate iframe srcdoc execution path. The internal-attribute filter for CVE-2026-47759 does not address this CVE. Comment/workflow storage and PSML HTML saves use server-side allowlist sanitizers. |
| Assessment date | 2026-11-14 |
Assessment
PageSeeder 6.3004 backports the TinyMCE SVG namespace-tracker correction while retaining TinyMCE version 6.8.6. Testing confirms that versions 6.0000–6.0014 shipped TinyMCE outside the published affected range; versions 6.1000–6.3003 ship affected editor assets; and version 6.3004 includes the backported fix. The build verifies the expected package version and patch pattern, and the shipped asset contains the corrected logic.
The reviewed comment/workflow sanitizer excludes SVG, MathML and event-handler attributes. The PSML HTML save route also applies a server-side allowlist sanitizer before conversion to PSML. These controls limit storage of the relevant malicious markup on the reviewed routes; no bypass of them was demonstrated.
A differential regression test reproduced the nested-SVG sanitization bypass on the original TinyMCE 6.8.6 asset and passed on the patched shipped asset. The full frontend test suite passed (56 suites, 431 tests), and the production build succeeded.
After the development server restart, the served TinyMCE asset contained the namespace correction. A Brave test of the PSML source editor also confirmed that iframe srcdoc content is sandboxed and a harmless execution marker did not run. This browser check verifies the separate iframe srcdoc sandbox control, not the SVG vulnerability addressed by this CVE; the differential regression test verifies the namespace fix.
This fixed determination applies to PageSeeder 6.3004. Versions 6.0000–6.0014 are not affected. Versions 6.1000–6.3003 ship affected TinyMCE assets. Custom templates, replaced assets and other editor integrations were not independently assessed.
Evidence includes the committed patch at repository revision e91c11f00d, shipped-asset inspection, differential jsdom regression tests and the local Brave check. A version-only scanner will still identify TinyMCE 6.8.6. The broad PSML editor schema may permit other active HTML and requires a separate security review.
Recommended action
Upgrade to PageSeeder 6.3004 or a later release
PageSeeder versions 6.1000–6.3003 ship TinyMCE assets affected by this vulnerability. Version 6.3004 includes a backported fix that corrects the SVG namespace handling.
If you cannot upgrade immediately, note that PageSeeder's server-side sanitization provides defense-in-depth protection on the reviewed storage routes. The comment/workflow sanitizer excludes SVG and event-handler attributes, and the PSML HTML save route applies allowlist sanitization before conversion. Upgrading remains the recommended mitigation.