Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm.NET NuGet🐘 Packagist

GHSA-q742-qvgc-gc2f

HIGH

TinyMCE Cross-Site Scripting (XSS) vulnerability using through data-mce- prefixed src, href, style attributes

Also known asCVE-2026-47759
Published
Jun 5, 2026
Updated
Jul 7, 2026
Affected
9 pkgs
Patched
6 / 9
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk20th percentile+0.04%
0.00%0.26%0.52%0.78%0.0%0.2%0.3%Jun 26Jul 26Jul 26

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

9 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

tinymcenpm
1.1Mdownloads / week

Description

Impact

Stored XSS vulnerability via unsanitized data-mce-* attributes (data-mce-href, data-mce-src, data-mce-style). Allows attackers to inject malicious values that override safe attributes during serialization, bypassing validation.

Patches

Patched by stripping unsafe data-mce-* attributes during parsing. Users should upgrade to the latest patched versions (5 LTS, 7.x, 8.x).

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 Tadi Kadango (website) and Ivan Babenko for their help identifying this vulnerability.

Affected Packages

9 total 6 fixed
EcosystemPackageVulnerable rangeFix
📦npmtinymceall versionsNo fix
📦npmtinymce6.0.0&&< 7.9.37.9.3
📦npmtinymce8.0.0&&< 8.5.18.5.1
.NETNuGetTinyMCEall versionsNo fix
.NETNuGetTinyMCE6.0.0&&< 7.9.37.9.3
.NETNuGetTinyMCE8.0.0&&< 8.5.18.5.1

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-q742-qvgc-gc2f 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-q742-qvgc-gc2f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Stored XSS vulnerability via unsanitized data-mce-* attributes (data-mce-href, data-mce-src, data-mce-style). Allows attackers to inject malicious values that override safe attributes during serialization, bypassing validation. ### Patches Patched by stripping unsafe data-mce-* attributes during parsing. Users should upgrade to the latest patched versions (5 LTS, 7.x, 8.x). ### 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
O3 Security · Impact-Aware SCA

Is GHSA-q742-qvgc-gc2f in your dependencies?

O3 detects GHSA-q742-qvgc-gc2f 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.