GHSA-C78W-2GW7-GJV3
Vulnerability from github – Published: 2020-05-11 20:00 – Updated: 2021-01-14 17:50Impact
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
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "tinymce"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.9.10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "tinymce"
},
"ranges": [
{
"events": [
{
"introduced": "5.0.0"
},
{
"fixed": "5.2.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-1010091"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2020-05-11T20:00:00Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "### Impact\nA 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.\n\n### Patches\nThis vulnerability has been patched in TinyMCE 4.9.10 and 5.2.2 by improved HTML parsing and sanitization logic.\n\n### Workarounds\nThe workarounds available are:\n- disable the media plugin and manually sanitize CDATA content (see below)\nor\n- upgrade to either TinyMCE 4.9.10 or TinyMCE 5.2.2\n\n#### Example: Manually strip CDATA elements\n```js\nsetup: function(editor) {\n editor.on(\u0027PreInit\u0027, function() {\n editor.parser.addNodeFilter(\u0027#cdata\u0027, function(nodes) {\n for (var i = 0; i \u003c nodes.length; i++) {\n nodes[i].remove();\n }\n });\n });\n}\n```\n\n### Acknowledgements\nTiny Technologies would like to thank Micha\u0142 Bentkowski and [intivesec](https://github.com/intivesec) for discovering these vulnerabilities.\n\n### References\nhttps://www.tiny.cloud/docs/release-notes/release-notes522/#securityfixes\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues)\n* Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)",
"id": "GHSA-c78w-2gw7-gjv3",
"modified": "2021-01-14T17:50:10Z",
"published": "2020-05-11T20:00:15Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/tinymce/tinymce/security/advisories/GHSA-c78w-2gw7-gjv3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-1010091"
},
{
"type": "WEB",
"url": "https://github.com/tinymce/tinymce/issues/4394"
}
],
"schema_version": "1.4.0",
"severity": [],
"summary": "XSS in TinyMCE"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.