How severe is GHSA-v65r-p3vv-jjfv?

GHSA-v65r-p3vv-jjfv has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-v65r-p3vv-jjfv?

GHSA-v65r-p3vv-jjfv affects the following packages: tinymce (npm), tinymce (npm), TinyMCE (NuGet), TinyMCE (NuGet), tinymce/tinymce (Packagist), tinymce/tinymce (Packagist). Ecosystems affected: npm, NuGet, Packagist.

How do I fix GHSA-v65r-p3vv-jjfv?

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.

How do I detect GHSA-v65r-p3vv-jjfv in my npm, NuGet, Packagist dependencies?

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.

How do I mitigate GHSA-v65r-p3vv-jjfv if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-v65r-p3vv-jjfv?

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.

Is GHSA-v65r-p3vv-jjfv actively exploited in the wild?

No public exploit code has been indexed for GHSA-v65r-p3vv-jjfv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-v65r-p3vv-jjfv?

GHSA-v65r-p3vv-jjfv has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v65r-p3vv-jjfv?

GHSA-v65r-p3vv-jjfv is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-v65r-p3vv-jjfv published, and has it been updated?

GHSA-v65r-p3vv-jjfv was published on October 19, 2023 and was last updated on February 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-v65r-p3vv-jjfv: tinymce Cross-Site Scripting (Medium 6.1)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk45th percentile-0.66%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

📦tinymce📦tinymce.NETTinyMCE.NETTinyMCE🐘tinymce/tinymce🐘tinymce/tinymce

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm, NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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

6 total 6 fixed

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 dependency

Detect
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

### Impact A [mutation cross-site scripting](https://researchgate.net/publication/266654651_mXSS_attacks_Attacking_well-secured_web-applications_by_using_innerHTML_mutations) (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](htt

O3 Security · Impact-Aware SCA

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.

Scan my dependencies How O3 SCA works

GHSA-v65r-p3vv-jjfv