GHSA-v65r-p3vv-jjfv
MEDIUMGHSA-v65r-p3vv-jjfv is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in tinymce. O3 Security confirms whether GHSA-v65r-p3vv-jjfv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
TinyMCE mXSS vulnerability in undo/redo, getContent API, resetContent API, and Autosave plugin
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
Impact
A mutation cross-site scripting (mXSS) vulnerability was discovered in TinyMCE’s core undo and redo functionality. When a carefully-crafted HTML snippet passes the XSS sanitisation layer, it is manipulated as a string by internal trimming functions before being stored in the undo stack. If the HTML snippet is restored from the undo stack, the combination of the string manipulation and reparative parsing by either the browser's native DOMParser API (TinyMCE 6) or the SaxParser API (TinyMCE 5) mutates the HTML maliciously, allowing an XSS payload to be executed. This vulnerability also impacts these related TinyMCE APIs and plugins:
Patches
This vulnerability has been patched in TinyMCE 5.10.8 and TinyMCE 6.7.1 by ensuring HTML is trimmed using node-level manipulation instead of string manipulation.
Fix
To avoid this vulnerability:
- Upgrade to TinyMCE 5.10.8 or higher for TinyMCE 5.x.
- Upgrade to TinyMCE 6.7.1 or higher for TinyMCE 6.x.
Acknowledgements
Tiny Technologies would like to thank Masato Kinugawa of Cure53 for discovering this vulnerability.
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 | ≥ 6.0.0&&< 6.7.1 | 6.7.1 |
| 📦npm | tinymce | all versions | 5.10.8 |
| .NETNuGet | TinyMCE | ≥ 6.0.0&&< 6.7.1 | 6.7.1 |
| .NETNuGet | TinyMCE | all versions | 5.10.8 |
| 🐘Packagist | tinymce/tinymce | ≥ 6.0.0&&< 6.7.1 | 6.7.1 |
| 🐘Packagist | tinymce/tinymce | all versions | 5.10.8 |
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 6.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v65r-p3vv-jjfv 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 GHSA-v65r-p3vv-jjfv 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 GHSA-v65r-p3vv-jjfv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v65r-p3vv-jjfv in your dependencies?
O3 detects GHSA-v65r-p3vv-jjfv 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.