Special characters in unescaped text nodes can trigger mXSS in TinyMCE
tinymce
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tinymce npm |
|
|
| tinymce/tinymce Packagist |
|
tinymce
| Product | Affected | Fixed in |
|---|---|---|
| tinymce npm |
|
|
| tinymce/tinymce Packagist |
|
5.10.96.7.3| TinyMCE NuGet |
|
|
TinyMCE is an open source rich text editor. A mutation cross-site scripting (mXSS) vulnerability was discovered in TinyMCE’s core undo/redo functionality and other APIs and plugins. Text nodes within specific parents are not escaped upon serialization according to the HTML standard. If such text nodes contain a special character reserved as an internal marker, they can be combined with other HTML patterns to form malicious snippets. These snippets pass the initial sanitisation layer when the content is parsed into the editor body, but can trigger XSS when the special internal marker is removed from the content and re-parsed. his vulnerability has been patched in TinyMCE versions 6.7.3 and 5.10.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
TinyMCE’s core undo/redo functionality and other APIs and plugins can improperly serialize certain text nodes. Crafted content can pass initial sanitisation and trigger cross-site scripting when an internal marker is removed and the content is re-parsed. The input does not specify authentication requirements or user interaction.
Teams using npm tinymce, Packagist tinymce/tinymce, or NuGet TinyMCE before 5.10.9 or from 6.0.0 through versions before 6.7.3 should check their installations.