Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47762 high CVSS 8.7

Cross-Site Scripting (XSS) in tinymce (CVE-2026-47762)

Summary

Cross-site scripting in tinymce (CVE-2026-47762). Confidential information can be exposed externally. Mitigation: upgrade to 8.5.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-47762 has been found in tinymce.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade tinymce to 8.5.1 or later.
If unsure, ask your IT team or search "tinymce CVE-2026-47762" on the vendor's site.

CVE-2026-47762 (tinymce) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Patched: 8.5.1 — apply immediately
Workaround: No official workaround available.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in tinymce.

📍 Affected scope

Check the vendor advisory for the affected versions of tinymce.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 8.5.1.

🛡️ Workaround

Workaround: No official workaround available.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tinymce' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'tinymce' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で tinymce を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    No official workaround available.

    パッチが適用されるまでの応急処置として、No official workaround available. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade tinymce to 8.5.1

    ステージング環境で 8.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm tinymce
[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.5.1"}]}]
nuget TinyMCE
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.5.1"}]}]
composer tinymce/tinymce
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Packagist tinymce/tinymce
[{"type":"ECOSYSTEM","events":[{"introduced":"8.0.0"},{"fixed":"8.5.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details