---
title: "CVE-2026-47762"
source: https://dev.pageseeder.com/guide/security/advisories/cve-2026-47762.html
description: "CVE-2026-47762 addresses unsafe restoration of protected comments in TinyMCE affecting PageSeeder 6.0000–6.3003. PageSeeder 6.3004 fixes this XSS vulnerability through application-level parser and serialization filters in all default editors."
last_updated: 2026-11-16T17:55:15+11:00
tokens: ~991
---

# CVE-2026-47762


        *TinyMCE: Unsafe restoration of protected comments*
      

| Property | Value |
| --- | --- |
| Published | 2026-05-28 |
| Last updated | 2026-11-16 |
| Component | TinyMCE |
| Severity | High |
| PageSeeder status | Fixed |

## Summary

Forged `mce:protected` comments can be decoded into unsanitized markup during TinyMCE content serialization. The upstream advisory describes an XSS risk when protected content is restored.

PageSeeder versions 6.1000 through 6.3003 inclusive are affected. PageSeeder 6.3004 fixes this behavior through application-level parser and serialization filters in all three default editors. The bundled TinyMCE version remains 6.8.6; upstream component fixes are available in 7.9.3 and 8.5.1.

The upstream High classification is CVSS 3.1: 8.7. Before the fix, testing demonstrated unsafe serialization without the protect option; it did not demonstrate end-to-end browser script execution or persistence. The same safety probe passes with the fix enabled.

For technical details, see the [upstream security advisory](https://github.com/tinymce/tinymce/security/advisories/GHSA-v98h-vmpc-fpqv).

## PageSeeder impact assessment

| Property | Value |
| --- | --- |
| Affected dependency | TinyMCE 6.8.6; application-level fix included in PageSeeder 6.3004 |
| PageSeeder versions assessed | Affected: PageSeeder 6.0000–6.3003 inclusive. Fixed: PageSeeder 6.3004; source and matching rebuilt frontend assets reviewed. |
| Vulnerability status | Fixed |
| Conditions required for exploitation |  |
| Relevant PageSeeder configuration |  |
| Assessment date | 2026-11-13 |

### Assessment

PageSeeder 6.3004 fixes this issue in the PSML editor, form editor and property markup editor. Forged protected comments are removed from parsed input, including setContent and insertContent, and from the DOM copy used by serialization. The second layer prevents a forged comment inserted directly into the editor body from being decoded into raw output markup.

The filter decodes protected comments in the same way as TinyMCE and accepts protected content only if it fully matches a configured protect pattern. PageSeeder does not configure protect, so standard editors reject all protected comments. Ordinary comments are preserved.

Regression tests use the real TinyMCE 6.8.6 editor. They reproduce the vulnerability without the filters and verify filtered setContent, insertContent and direct-DOM cases, preservation of ordinary comments, and legitimate protected content when explicitly configured.

The independent safety probe that previously returned an image with an onerror attribute now returns only the surrounding paragraphs. It passes with the fix enabled. The full frontend suite passes 428 tests across 55 suites, and lint passes for the security helper and its test file.

The reviewed comment/workflow and PSML HTML storage routes also use server-side allowlist sanitizers. The affected-version classification concerns vulnerable editor behavior; a bypass of these storage controls was not demonstrated. Version-only scanners can continue to report TinyMCE 6.8.6 despite the PageSeeder application-level fix.

The affected version range is consistent with the other advisories in this set and with the TinyMCE advisory which specified the affected product versions. The fix was verified in source and matching rebuilt frontend assets on 13 November 2026. Custom editor integrations and independently replaced components may have different exposure.

## 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.

## References

- 
          [CVE-2026-47762 record](https://www.cve.org/CVERecord?id=CVE-2026-47762)
        
- 
          [Upstream security advisory](https://github.com/tinymce/tinymce/security/advisories/GHSA-v98h-vmpc-fpqv)
        

