CVE-2024-38356 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in tinymce. O3 Security confirms whether CVE-2024-38356 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
TinyMCE Cross-Site Scripting (XSS) vulnerability using noneditable_regexp option
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
tinymcenpmDescription
TinyMCE is an open source rich text editor. A cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content extraction code. When using the noneditable_regexp option, specially crafted HTML attributes containing malicious code were able to be executed when content was extracted from 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, when using the noneditable_regexp option, any content within an attribute is properly verified to match the configured regular expression before being added. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | tinymce | all versions | 5.11.0 |
| 📦npm | tinymce | ≥ 6.0.0&&< 6.8.4 | 6.8.4 |
| 📦npm | tinymce | ≥ 7.0.0&&< 7.2.0 | 7.2.0 |
| .NETNuGet | TinyMCE | all versions | 5.11.0 |
| .NETNuGet | TinyMCE | ≥ 6.0.0&&< 6.8.4 | 6.8.4 |
| .NETNuGet | TinyMCE | ≥ 7.0.0&&< 7.2.0 | 7.2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tinymce. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update tinymce to 5.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38356 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-38356 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-38356. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-38356 in your dependencies?
O3 detects CVE-2024-38356 across npm, NuGet, Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.