MediumGHSA-w9jx-4g6g-rp7xCVE-2024-38357PYSEC-2026-1302

TinyMCE Cross-Site Scripting (XSS) vulnerability using noscript elements

Published 19 Jun 2024 · Updated 10 Sept 2026

Affected packages

Affected
<5.11.0
Fixed in
5.11.0
Update to the fixed version for your release line, for example:npm install tinymce@5.11.0
Affected
<5.11.0
Fixed in
5.11.0
Update to the fixed version for your release line, for example:composer require tinymce/tinymce:^5.11.0
Affected
>=6.0.0 <6.8.4
Fixed in
6.8.4
Update to the fixed version for your release line, for example:npm install tinymce@6.8.4
Affected
>=7.0.0 <7.2.0
Fixed in
7.2.0
Update to the fixed version for your release line, for example:npm install tinymce@7.2.0
Affected
>=6.0.0 <6.8.4
Fixed in
6.8.4
Update to the fixed version for your release line, for example:composer require tinymce/tinymce:^6.8.4
Affected
>=7.0.0 <7.2.0
Fixed in
7.2.0
Update to the fixed version for your release line, for example:composer require tinymce/tinymce:^7.2.0

Details

Impact

A cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content parsing code. This allowed specially crafted noscript elements containing malicious code to be executed when that content was loaded into the editor.

Patches

This vulnerability has been patched in TinyMCE 7.2.0, TinyMCE 6.8.4 and TinyMCE 5.11.0 LTS by ensuring that content within noscript elements are properly parsed.

Fix

To avoid this vulnerability:

  • Upgrade to TinyMCE 7.2.0 or higher.
  • Upgrade to TinyMCE 6.8.4 or higher for TinyMCE 6.x.
  • Upgrade to TinyMCE 5.11.0 LTS or higher for TinyMCE 5.x (only available as part of commercial long-term support contract).

Acknowledgements

Tiny thanks Malav Khatri and another reporter for their help identifying this vulnerability.

References

For more information

If you have any questions or comments about this advisory:

  • Email us at [infosec@tiny.cloud](mailto:infosec@tiny.cloud)
  • Open an issue in the TinyMCE repo

Is GHSA-w9jx-4g6g-rp7x 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.