How severe is CVE-2026-47762?

CVE-2026-47762 has a CVSS score of 8.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-47762?

CVE-2026-47762 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 CVE-2026-47762?

No patched version of tinymce has shipped for CVE-2026-47762 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 CVE-2026-47762 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 CVE-2026-47762 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 CVE-2026-47762 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-47762 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 CVE-2026-47762?

CVE-2026-47762 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 19th 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 CVE-2026-47762?

CVE-2026-47762 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 CVE-2026-47762 published, and has it been updated?

CVE-2026-47762 was published on May 28, 2026 and was last updated on October 20, 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

CVE-2026-47762 — tinymce

HIGH

CVE-2026-47762 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.

TinyMCE Cross-Site Scripting (XSS) vulnerability through `mce:protected` comments

Also known asGHSA-v98h-vmpc-fpqv

Published

May 28, 2026

Updated

Oct 20, 2026

Affected

9 pkgs

Patched

6 / 9

Exploits

None indexed

Exploitation data as of Oct 19, 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 CVE-2026-47762.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk-0.13%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2026-47762 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 391,411 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

574Kdownloads / week

Description

Impact

Stored XSS vulnerability via forged mce:protected comments. Allows attackers to bypass sanitization and inject scripts that execute when content is restored. Impacts users who utilize the protect option.

Patches

Patched by validating decoded mce:protected content against configured protect regex rules before restoring. Users should upgrade to the latest patched version.

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 Ivan Babenko 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 CVE-2026-47762 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 via forged mce:protected comments. Allows attackers to bypass sanitization and inject scripts that execute when content is restored. Impacts users who utilize the protect option. ### Patches Patched by validating decoded mce:protected content against configured protect regex rules before restoring. Users should upgrade to the latest patched version. ### 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 TinyM