← Back
CVE-2026-62324
medium
CVSS 5.4
Cross-Site Scripting (XSS) in jodit (CVE-2026-62324)
Summary
cross-site scripting in jodit (CVE-2026-62324). Risk of unauthorized operations or information disclosure. Exploitable via ``sanitizeHTMLElement``. Mitigation: upgrade to `4.12.31` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-62324** has been found in jodit.
Attackers can target a specific entry point like ``sanitizeHTMLElement`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade jodit to **4.12.31** or later.
If unsure, ask your IT team or search "jodit CVE-2026-62324" on the vendor's site.
CVE-2026-62324 (jodit) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: `sanitizeHTMLElement` / `href` / `isDangerousUrl` / `innerHTML`
Patched: `4.12.31` — 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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in jodit. Attackers reach the vulnerable code path via ``sanitizeHTMLElement`` without authentication.
📍 Affected scope
jodit — . Attack surface: `sanitizeHTMLElement` / `href` / `isDangerousUrl` / `innerHTML`.
🔥 Severity
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.12.31**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'jodit' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'jodit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `jodit` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade jodit to 4.12.31ステージング環境で 4.12.31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
jodit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.31"}]}]