CVE-2024-38357 is a cross-site scripting vulnerability in TinyMCE caused by improper parsing of content contained within HTML noscript elements. Specially crafted content embedded inside a noscript element can bypass expected neutralization during TinyMCE content parsing and execute when the content is loaded into the editor. The flaw resides in the editor’s content parsing logic, which did not correctly handle noscript element contents as untrusted input. TinyMCE addressed the issue by ensuring content within noscript elements is properly parsed before being processed by the editor.
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 XSS vulnerability mentioned as historical context.
A prior TinyMCE XSS vulnerability in content insertion code mentioned as historical background.
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.