XSS in TinyMCE
Published 11 May 2020 · Updated 8 Nov 2023
Affected packages
- Affected
- <4.9.10
- Fixed in
- 4.9.10
npm install tinymce@4.9.10- Affected
- >=5.0.0 <5.2.2
- Fixed in
- 5.2.2
npm install tinymce@5.2.2Details
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.
Patches
This vulnerability has been patched in TinyMCE 4.9.10 and 5.2.2 by improved HTML parsing and sanitization logic.
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 [infosec@tiny.cloud](mailto:infosec@tiny.cloud)
Is GHSA-c78w-2gw7-gjv3 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected tinymce, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.