Quick answers
- Is CVE-2026-47760 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47760 being exploited in the wild.
- How severe is CVE-2026-47760?
- High severity, with a CVSS score of 8.7, published 28 May 2026.
- Which products and versions are affected?
- tinymce (npm) >= 6.8.0, < 7.1.0, SEMVER:introduced=6.8.0,fixed=7.1.0; tinymce/tinymce (Packagist) >= 6.8.0, < 7.1.0.
- Is there a fix for CVE-2026-47760?
- Yes. tinymce (npm): upgrade to 7.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47760 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47760?
- Check whether you run tinymce (npm) 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.
How to fix
- tinymce (npm): upgrade to 7.1.0 or later
npm install tinymce@7.1.0
Technical details
A Cross-Site Scripting (XSS) vulnerability exists in TinyMCE versions 6.8.0 through 7.0.x. The root cause is improper SVG namespace scope handling within the editor's HTML sanitizer. By crafting a payload using nested <svg> elements, an attacker can bypass attribute sanitization to execute arbitrary JavaScript. Exploitation requires network access and low privileges to submit content, plus interaction from another user to view the malicious content. The issue is resolved in TinyMCE version 7.1.0 through a rewrite of the affected sanitization logic.
Affected products
- Tiny TinyMCE >= 6.8.0, < 7.1.0
Identifiers
- CVE-2026-47760
- GHSA-mh5m-5hw4-5c69
Timeline
- 2026-05-20: disclosed: Initial disclosure to vendor
- 2026-05-28: advisory: NVD publication date
- 2026-06-05: advisory: GitHub Advisory Database publication date