How severe is GHSA-vg35-5wq7-3x7w?

GHSA-vg35-5wq7-3x7w has a CVSS score of 8.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vg35-5wq7-3x7w?

GHSA-vg35-5wq7-3x7w affects the following packages: tinymce (npm), tinymce (npm), tinymce (npm), TinyMCE (NuGet), TinyMCE (NuGet), TinyMCE (NuGet), tinymce/tinymce (Packagist), tinymce/tinymce (Packagist), and 1 more. Ecosystems affected: npm, NuGet, Packagist.

How do I fix GHSA-vg35-5wq7-3x7w?

No patched version of tinymce has shipped for GHSA-vg35-5wq7-3x7w yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-vg35-5wq7-3x7w 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-vg35-5wq7-3x7w 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-vg35-5wq7-3x7w actively exploited in the wild?

No public exploit code has been indexed for GHSA-vg35-5wq7-3x7w 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-vg35-5wq7-3x7w?

GHSA-vg35-5wq7-3x7w has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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-vg35-5wq7-3x7w?

GHSA-vg35-5wq7-3x7w 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-vg35-5wq7-3x7w published, and has it been updated?

GHSA-vg35-5wq7-3x7w was published on June 5, 2026 and was last updated on September 10, 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

HIGH severity

TinyMCE Cross-Site Scripting (XSS) vulnerability using media plugin `data-mce-object` injectionGHSA-vg35-5wq7-3x7w

HIGH

GHSA-vg35-5wq7-3x7w is a high-severity (CVSS 8.7) 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-47761

Published

Jun 5, 2026

Updated

Sep 10, 2026

Affected

9 pkgs

Patched

6 / 9

Exploits

None indexed

Exploitation data as of Oct 18, 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-vg35-5wq7-3x7w.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.15%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-vg35-5wq7-3x7w by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 390,807 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

9 pkgs affected

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.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

tinymcenpm

605Kdownloads / week

Description

Impact

Stored XSS vulnerability in the media plugin. Attackers can inject malicious scripts via crafted data-mce-* attributes, which are executed when content is rendered. Impacts users of TinyMCE with the media plugin enabled.

Patches

This vulnerability has been patched in TinyMCE 8.5.1, TinyMCE 7.9.3 and TinyMCE 5.11.1 LTS by ensuring that, when using the media plugin, any content with data-mce-object and data-mce-p-* attributes are properly sanitized.

Workarounds

No official workaround available.

Fix

To avoid this vulnerability:

Upgrade to TinyMCE 8.5.1 or higher.
Upgrade to TinyMCE 7.9.3 or higher.
Upgrade to TinyMCE 5.11.1 LTS or higher for TinyMCE 5.x (only available as part of commercial long-term support contract).

Acknowledgements

Tiny thanks Aymane MAZGUITI and Ange Primiterra for their help identifying this vulnerability.

Affected Packages

9 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`tinymce`	all versions	No fix
📦npm	`tinymce`	≥ 6.0.0&&< 7.9.3	7.9.3`npm install tinymce@7.9.3`
📦npm	`tinymce`	≥ 8.0.0&&< 8.5.1	8.5.1`npm install tinymce@8.5.1`
.NETNuGet	`TinyMCE`	all versions	No fix
.NETNuGet	`TinyMCE`	≥ 6.0.0&&< 7.9.3	7.9.3`dotnet add package TinyMCE --version 7.9.3`
.NETNuGet	`TinyMCE`	≥ 8.0.0&&< 8.5.1	8.5.1`dotnet add package TinyMCE --version 8.5.1`

Affected Products

1 product · 3 configurations

Application

tinymcetiny

≥ 8.0.0 && < 8.5.1

range

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
No patched version of tinymce has shipped for GHSA-vg35-5wq7-3x7w yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 crafted `data-mce-*` attributes, which are executed when content is rendered. Impacts users of TinyMCE with the media plugin enabled. ### Patches This vulnerability has been patched in TinyMCE 8.5.1, TinyMCE 7.9.3 and TinyMCE 5.11.1 LTS by ensuring that, when using the media plugin, any content with `data-mce-object` and `data-mce-p-*` attributes are properly sanitized. ### Workarounds No official workaround available. ### Fix To avoid this vulnerability: - Upgrade to TinyMCE 8.5.1 or higher