CVE-2026-47762
Stored XSS in TinyMCE via forged mce:protected comments
Is CVE-2026-47762 being exploited?
Not confirmed. CVE-2026-47762 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-47762?
CVE-2026-47762 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47762?
Yes. A fix has been recorded for CVE-2026-47762. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47762 affect?
CVE-2026-47762 affects TinyMCE editor (<5.11.1, <7.9.3, <8.5.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47762?
Upgrade to fixed versions: 5.11.1+, 7.9.3+, or 8.5.1+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stored XSS via forged mce:protected comments; scripts run when content is restored, enabling session hijack, data theft, or defacement in apps using Protect option.
Patch when possible
- affected< 5.11.1
- affected>= 6.0.0 and <= 6.8.6
- affected>= 7.0.0 and < 7.9.3
- affected>= 8.0.0 and < 8.5.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.