How severe is GHSA-mf2p-h6hf-fcwm?

No CVSS score has been assigned to GHSA-mf2p-h6hf-fcwm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mf2p-h6hf-fcwm?

GHSA-mf2p-h6hf-fcwm 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-mf2p-h6hf-fcwm?

Update tinymce to 8.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf2p-h6hf-fcwm is resolved across your whole dependency graph.

How do I detect GHSA-mf2p-h6hf-fcwm in my npm, NuGet, Packagist dependencies?

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.

How do I mitigate GHSA-mf2p-h6hf-fcwm if there is no patch (or I can't update yet)?

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.

Is GHSA-mf2p-h6hf-fcwm actively exploited in the wild?

No public exploit code has been indexed for GHSA-mf2p-h6hf-fcwm 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-mf2p-h6hf-fcwm?

GHSA-mf2p-h6hf-fcwm has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 28th 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-mf2p-h6hf-fcwm?

GHSA-mf2p-h6hf-fcwm 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-mf2p-h6hf-fcwm published, and has it been updated?

GHSA-mf2p-h6hf-fcwm was published on October 27, 2026 and was last updated on October 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm.NET NuGet🐘 Packagist

Not in CISA KEV

TinyMCE Cross-Site Scripting (XSS) vulnerability using media plugin `data-mce-object` serializationGHSA-mf2p-h6hf-fcwm

Fix: tinymce/tinymce@bd1ab5e

GHSA-mf2p-h6hf-fcwm is a Cross-site Scripting (XSS) vulnerability in tinymce. A fix is available for tinymce — see the affected versions and patch details below.

Also known asCVE-2026-116675

Published

Oct 27, 2026

Updated

Oct 27, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-mf2p-h6hf-fcwm.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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

Stored XSS vulnerability in the media plugin. Attackers can inject malicious scripts via elements crafted through the data-mce-object attribute, which are created and executed before sanitization. Impacts users of TinyMCE with the media plugin enabled.

Patches

This vulnerability has been patched in TinyMCE 8.9.3 and TinyMCE 7.9.4 by ensuring that, when using the media plugin, any content created through the data-mce-object attribute is properly sanitized first.

Workarounds

No official workaround available.

Fix

To avoid this vulnerability:

Upgrade to TinyMCE 8.9.3 or higher. Upgrade to TinyMCE 7.9.4 or higher.

Acknowledgements

Tiny thanks Fariskhi Vidyan and David Vieira Kurz (HiSolutions AG) for their help identifying this vulnerability.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`tinymce`	≥ 8.5.1&&< 8.9.3	8.9.3`npm install tinymce@8.9.3`
📦npm	`tinymce`	≥ 7.9.3&&< 7.9.4	7.9.4`npm install tinymce@7.9.4`
.NETNuGet	`TinyMCE`	≥ 8.5.1&&< 8.9.3	8.9.3`dotnet add package TinyMCE --version 8.9.3`
.NETNuGet	`TinyMCE`	≥ 7.9.3&&< 7.9.4	7.9.4`dotnet add package TinyMCE --version 7.9.4`
🐘Packagist	`tinymce/tinymce`	≥ 8.5.1&&< 8.9.3	8.9.3`composer require tinymce/tinymce:^8.9.3`
🐘Packagist	`tinymce/tinymce`	≥ 7.9.3&&< 7.9.4	7.9.4`composer require tinymce/tinymce:^7.9.4`

Detection & mitigation playbook

Open-source dependency

Detect
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 8.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf2p-h6hf-fcwm 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

### Impact Stored XSS vulnerability in the media plugin. Attackers can inject malicious scripts via elements crafted through the data-mce-object attribute, which are created and executed before sanitization. Impacts users of TinyMCE with the media plugin enabled. ### Patches This vulnerability has been patched in TinyMCE 8.9.3 and TinyMCE 7.9.4 by ensuring that, when using the media plugin, any content created through the data-mce-object attribute is properly sanitized first. ### Workarounds No official workaround available. ### Fix To avoid this vulnerability: Upgrade to TinyMCE 8.9.3 or

O3 Security · Impact-Aware SCA

Is GHSA-mf2p-h6hf-fcwm in your dependencies?

Find it across npm, NuGet, Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works