TinyMCE Cross-Site Scripting (XSS) vulnerability using noneditable_regexp optionGHSA-9hcv-j9pv-qmph
MEDIUMFix: tinymce/tinymce@5acb741GHSA-9hcv-j9pv-qmph is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in tinymce. A fix is available for tinymce — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9hcv-j9pv-qmph.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
tinymcenpmDescription
Impact
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.
Patches
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.
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).
References
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
- Open an issue in the TinyMCE repo
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | tinymce | all versions | 5.11.0npm install tinymce@5.11.0 |
| 📦npm | tinymce | ≥ 6.0.0&&< 6.8.4 | 6.8.4npm install tinymce@6.8.4 |
| 📦npm | tinymce | ≥ 7.0.0&&< 7.2.0 | 7.2.0npm install tinymce@7.2.0 |
| .NETNuGet | TinyMCE | all versions | 5.11.0dotnet add package TinyMCE --version 5.11.0 |
| .NETNuGet | TinyMCE | ≥ 6.0.0&&< 6.8.4 | 6.8.4dotnet add package TinyMCE --version 6.8.4 |
| .NETNuGet | TinyMCE | ≥ 7.0.0&&< 7.2.0 | 7.2.0dotnet add package TinyMCE --version 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tinymce to 5.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hcv-j9pv-qmph is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-9hcv-j9pv-qmph in your dependencies?
Find it across npm, NuGet, Packagist, including transitive dependencies.