Summary
XSS in TinyMCE
Workarounds
The workarounds available are:
- disable the media plugin and manually sanitize CDATA content (see below)
or - upgrade to either TinyMCE 4.9.10 or TinyMCE 5.2.2
Example: Manually strip CDATA elements
setup: function(editor) {
editor.on('PreInit', function() {
editor.parser.addNodeFilter('#cdata', function(nodes) {
for (var i = 0; i < nodes.length; i++) {
nodes[i].remove();
}
});
});
}
Acknowledgements
Tiny Technologies would like to thank Michał Bentkowski and intivesec for discovering these vulnerabilities.
References
https://www.tiny.cloud/docs/release-notes/release-notes522/#securityfixes
For more information
If you have any questions or comments about this advisory:
- Open an issue in the TinyMCE repo
- Email us at [email protected]
Impact
A cross-site scripting (XSS) vulnerability was discovered in: the core parser and media plugin. The vulnerability allowed arbitrary JavaScript execution when inserting a specially crafted piece of content into the editor via the clipboard or APIs. This impacts all users who are using TinyMCE 4.9.9 or lower and TinyMCE 5.2.1 or lower.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This vulnerability has been patched in TinyMCE 4.9.10 and 5.2.2 by improved HTML parsing and sanitization logic.
Frequently Asked Questions
- What is CVE-2019-1010091? CVE-2019-1010091 is a medium-severity cross-site scripting (XSS) vulnerability in tinymce (npm), affecting versions < 4.9.10. It is fixed in 4.9.10, 5.2.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of tinymce are affected by CVE-2019-1010091? tinymce (npm) versions < 4.9.10 is affected.
- Is there a fix for CVE-2019-1010091? Yes. CVE-2019-1010091 is fixed in 4.9.10, 5.2.2. Upgrade to this version or later.
- Is CVE-2019-1010091 exploitable, and should I be worried? Whether CVE-2019-1010091 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2019-1010091 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2019-1010091?
- Upgrade
tinymceto 4.9.10 or later - Upgrade
tinymceto 5.2.2 or later
- Upgrade