CVE-2023-45818 is a mutation cross-site scripting vulnerability in TinyMCE. The flaw is in core undo and redo handling, and also affects content restoration paths including the getContent API, resetContent API, and the Autosave plugin. A carefully crafted HTML fragment can pass TinyMCE’s XSS sanitization layer, then be altered by internal trimming logic that manipulates the HTML as a string before storing it in the undo stack. When that content is later restored, reparative parsing by the browser DOMParser in TinyMCE 6 or the SaxParser in TinyMCE 5 can mutate the markup into an executable form, causing attacker-controlled script execution in the rendered page. The issue was fixed by replacing string-based trimming with node-level HTML manipulation.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A prior TinyMCE mutation-XSS vulnerability mentioned for comparison.
A historical TinyMCE XSS vulnerability mentioned only as background in the vendor security history table.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.