Vulnerability in django-tinymce (CVE-2024-21910)
Summary
Vulnerability in django-tinymce (CVE-2024-21910). Risk of unauthorized operations or information disclosure. Exploitable via image. Mitigation: upgrade to 3.4.0 or later.
Original description
The description as published by the source.
TinyMCE versions before 5.10.0 are affected by a cross-site scripting vulnerability. A remote and unauthenticated attacker could introduce crafted image or link URLs that would result in the execution of arbitrary JavaScript in an editing user's browser.
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-2024-21910 has been found in django-tinymce.
Attackers can target a specific entry point like image over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade django-tinymce to 3.4.0 or later.
If unsure, ask your IT team or search "django-tinymce CVE-2024-21910" on the vendor's site.
CVE-2024-21910 (django-tinymce) — CWE-64 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: image / link
Patched: 3.4.0 — apply immediately
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.
A vulnerability (CWE-64) exists in django-tinymce. Attackers reach the vulnerable code path via image without authentication.
Check the vendor advisory for the affected versions of django-tinymce. Attack surface: image / link.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django-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
-
1Identify exposure identify
grep -r 'django-tinymce' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
django-tinymceを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade django-tinymce to 3.4.0ステージング環境で 3.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package pypi.org
- package github.com
- package pypi.org
- report github.com
- web github.com
- web pypi.org
- web nuget.org