Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Medium

Stored XSS in TinyMCE via unsanitized data-mce-* attributes

IdentifiersCVE-2026-47759CWE-79· Improper Neutralization of Input…

CVE-2026-47759 is a stored cross-site scripting vulnerability in TinyMCE affecting versions prior to 5.11.1, 7.9.3, and 8.5.1. The flaw is caused by improper handling of internal data-mce-* attributes, specifically data-mce-href, data-mce-src, and data-mce-style. TinyMCE preserves user-entered values in these attributes during editing, then during serialization and content generation (for example when editor.getContent() is invoked), it copies those values back into the corresponding standard href, src, and style attributes. While TinyMCE validates standard href and src attributes against unsafe protocols, equivalent schema-level validation is not applied to the data-mce-* variants. As a result, attacker-controlled malicious values can be stored in data-mce-* attributes and later overwrite previously sanitized attributes during serialization, bypassing validation and producing stored XSS in rendered content.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation allows attacker-controlled script or script-capable payloads to be persisted in TinyMCE-managed content and executed when that content is later rendered in a victim's browser. This can lead to session compromise, execution of arbitrary JavaScript in the application origin, theft of sensitive data accessible to the browser session, unauthorized actions on behalf of the victim, and broader compromise of applications embedding TinyMCE where untrusted content is stored and viewed.

Mitigation

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

No official workaround is available in the provided content. Until patching, reduce exposure by preventing untrusted users from submitting or storing HTML content processed by vulnerable TinyMCE instances, restricting where stored editor content is rendered, and applying additional server-side sanitization or filtering for dangerous href, src, style, and data-mce-* attributes before storage and before presentation.

Remediation

Patch, then assume compromise.

Upgrade TinyMCE to a fixed release: 5.11.1 for the 5.x branch, 7.9.3 for the 7.x branch, or 8.5.1 for the 8.x branch, or later supported versions. According to the provided advisory, the fix strips unsafe data-mce-* attributes during parsing, preventing malicious internal attribute values from overriding sanitized standard attributes during serialization.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.