Is CVE-2026-47762 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47762 being exploited in the wild.

How severe is CVE-2026-47762?

High severity, with a CVSS score of 8.7, published 28 May 2026.

Which products and versions are affected?

tinymce (npm) SEMVER:introduced=0,last_affected=5.10.9; TinyMCE (NuGet) ECOSYSTEM:introduced=0,last_affected=5.10.9; tinymce/tinymce (Packagist) ECOSYSTEM:introduced=0,last_affected=5.10.9.

Is there a fix for CVE-2026-47762?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-47762 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47762?

Check whether you run tinymce (npm), TinyMCE (NuGet) or tinymce/tinymce (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47762: Tiny Technologies TinyMCE stored XSS via forged mce:protected comments

CVE-2026-47762 · Severity: high · CVSS 8.7 · Published 2026-05-28

TinyMCE, a widely used rich text editor for web applications, is vulnerable to a security flaw that allows attackers to inject malicious scripts into saved content. If a user views or edits this compromised content, the script can execute in their browser, potentially leading to unauthorized data access or account takeover. This issue specifically affects organizations using the editor's content protection features.

Technologies: tinymce (npm), TinyMCE (NuGet), tinymce/tinymce (Packagist). Vendors: npm, NuGet, Packagist.

Quick answers

Is CVE-2026-47762 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47762 being exploited in the wild.
How severe is CVE-2026-47762?: High severity, with a CVSS score of 8.7, published 28 May 2026.
Which products and versions are affected?: tinymce (npm) SEMVER:introduced=0,last_affected=5.10.9; TinyMCE (NuGet) ECOSYSTEM:introduced=0,last_affected=5.10.9; tinymce/tinymce (Packagist) ECOSYSTEM:introduced=0,last_affected=5.10.9.
Is there a fix for CVE-2026-47762?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47762 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47762?: Check whether you run tinymce (npm), TinyMCE (NuGet) or tinymce/tinymce (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stored cross-site scripting (XSS) vulnerability exists in TinyMCE due to improper neutralization of 'mce:protected' comments. Attackers can bypass the editor's sanitization filters by forging these comments, which are intended to protect specific code blocks from being altered. When the editor restores the content for display or editing, the malicious payload is executed in the context of the user's session. The vulnerability requires low privileges to submit content and some user interaction to view the affected page. The fix involves validating decoded protected content against configured regex rules before restoration.

Affected products

Tiny TinyMCE < 5.11.1, >= 6.0.0, < 7.9.3, >= 8.0.0, < 8.5.1

Identifiers

CVE-2026-47762
GHSA-v98h-vmpc-fpqv

Timeline

2026-05-20: disclosed
2026-05-28: advisory: NVD publication date
2026-06-05: advisory: GitHub Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.