# CVE-2024-38357: TinyMCE Cross-Site Scripting (XSS) vulnerability using noscript elements > Attackers can execute malicious scripts via crafted noscript elements in TinyMCE, requiring users to upgrade to patched versions. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Jun 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-w9jx-4g6g-rp7x, PYSEC-2026-1302, UBUNTU-CVE-2024-38357 ## What is CVE-2024-38357? CVE-2024-38357 is a medium-severity cross-site scripting vulnerability in tinymce, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description TinyMCE is an open source rich text editor. 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. 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. Users are advised to upgrade. There are no known workarounds for this vulnerability. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-38357? 21 open source packages ship an affected version, including TinyMCE, tinymce/tinymce and django-tinymce. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `TinyMCE` | NuGet | All versions | 5.11.0 | | `TinyMCE` | NuGet | All versions | 5.11.0 | | `TinyMCE` | NuGet | From 6.0.0 | 6.8.4 | | `TinyMCE` | NuGet | From 6.0.0 | 6.8.4 | | `TinyMCE` | NuGet | From 7.0.0 | 7.2.0 | | `TinyMCE` | NuGet | From 7.0.0 | 7.2.0 | | `tinymce/tinymce` | Packagist | All versions | 5.11.0 | | `tinymce/tinymce` | Packagist | All versions | 5.11.0 | | `tinymce/tinymce` | Packagist | From 6.0.0 | 6.8.4 | | `tinymce/tinymce` | Packagist | From 6.0.0 | 6.8.4 | | `tinymce/tinymce` | Packagist | From 7.0.0 | 7.2.0 | | `tinymce/tinymce` | Packagist | From 7.0.0 | 7.2.0 | | `django-tinymce` | PyPI | All versions | 4.1.0 | | `django-tinymce` | PyPI | All versions | 4.1.0 | | `django-tinymce` | PyPI | All versions | 4.1.0 | | `tinymce` | npm | All versions | 5.11.0 | | `tinymce` | npm | All versions | 5.11.0 | | `tinymce` | npm | From 6.0.0 | 6.8.4 | | `tinymce` | npm | From 6.0.0 | 6.8.4 | | `tinymce` | npm | From 7.0.0 | 7.2.0 | | `tinymce` | npm | From 7.0.0 | 7.2.0 | ## How do I fix CVE-2024-38357? Upgrade TinyMCE to a fixed version for your release line: 5.11.0, 6.8.4 or 7.2.0. ## Is CVE-2024-38357 being exploited? There is no known exploitation of CVE-2024-38357 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38357 and fix it if it is affected. What it is: CVE-2024-38357 is a medium-severity cross-site scripting vulnerability in tinymce, published on 19 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-38357 in the wild and no public exploit code. Affected packages and fixed versions: - TinyMCE (NuGet): affected all versions; fixed in 5.11.0 - TinyMCE (NuGet): affected all versions; fixed in 5.11.0 - TinyMCE (NuGet): affected from 6.0.0; fixed in 6.8.4 - TinyMCE (NuGet): affected from 6.0.0; fixed in 6.8.4 - TinyMCE (NuGet): affected from 7.0.0; fixed in 7.2.0 - TinyMCE (NuGet): affected from 7.0.0; fixed in 7.2.0 - tinymce/tinymce (Packagist): affected all versions; fixed in 5.11.0 - tinymce/tinymce (Packagist): affected all versions; fixed in 5.11.0 - tinymce/tinymce (Packagist): affected from 6.0.0; fixed in 6.8.4 - tinymce/tinymce (Packagist): affected from 6.0.0; fixed in 6.8.4 - tinymce/tinymce (Packagist): affected from 7.0.0; fixed in 7.2.0 - tinymce/tinymce (Packagist): affected from 7.0.0; fixed in 7.2.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-38357/ (Markdown: https://insights.sbomify.com/CVE-2024-38357/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38357 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38357 - OSV: https://osv.dev/vulnerability/CVE-2024-38357 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38357/ Summaries are generated and may contain mistakes; the official description above is the record.