Skip to main content
Mallory
MediumVulnerability

CVE-2026-47760: Stored XSS in TinyMCE sanitizer SVG namespace handling

Published May 28, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.4Medium · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Tiny Software
IdentifiersCVE-2026-47760CWE-79 · Improper Neutralization of Input…

CVE-2026-47760 is a stored cross-site scripting vulnerability in TinyMCE affecting versions 6.8.0 through versions prior to 7.1.0. The flaw is caused by improper SVG namespace scope handling in the editor’s sanitizer. When processing crafted nested SVG content, the sanitizer can lose track of the active namespace and fail to remove dangerous attributes, allowing malicious event-handler attributes to survive sanitization. An authenticated attacker who can submit content processed by TinyMCE can inject a crafted payload that is stored and later rendered to other users. When a victim views or interacts with the malicious content, arbitrary JavaScript executes in the browser context of the hosting application.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables execution of attacker-controlled JavaScript in the browser session of users who view the crafted content. Because the script runs in the context of the hosting application, impact can include session hijacking, credential or token theft, DOM manipulation, unauthorized actions performed as the victim, and exfiltration of sensitive data accessible to the application context. The vulnerability has scope change because compromise extends from stored editor content into the broader web application context.

Mitigation

If you can’t patch tonight, do this now.

No official workaround is available. As defense in depth, organizations can reduce exposure by enforcing a strict Content Security Policy, performing server-side validation and sanitization of submitted rich-text content, restricting or disallowing SVG content where feasible, and hardening session protections such as HttpOnly and Secure cookie settings. These measures do not replace upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade TinyMCE to version 7.1.0 or later. The vulnerability is fixed in 7.1.0 through changes to the affected sanitizer logic. TinyMCE 6.x is end-of-life and will not receive a patch for this issue, so deployments on that branch should migrate to a supported release.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Tiny SoftwareTinymceapplication
FAQ

Frequently asked questions

Is CVE-2026-47760 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-47760 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-47760?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-47760.
Is there a patch for CVE-2026-47760?
Upgrade TinyMCE to version 7.1.0 or later. The vulnerability is fixed in 7.1.0 through changes to the affected sanitizer logic.
What products are affected by CVE-2026-47760?
Tiny Software Tinymce.
How severe is CVE-2026-47760?
CVE-2026-47760 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.19% (9th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.