← Back
CVE-2026-56394
medium
CVSS 6.5
Path Traversal in craftcms/cms (CVE-2026-56394)
Summary
path traversal in craftcms/cms (CVE-2026-56394). Confidential information can be exposed externally. Exploitable via ``extension``. Mitigation: upgrade to `5.9.13` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-56394** has been found in craftcms/cms.
Attackers can target a specific entry point like ``extension`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade craftcms/cms to **5.9.13** or later.
If unsure, ask your IT team or search "craftcms/cms CVE-2026-56394" on the vendor's site.
CVE-2026-56394 (craftcms/cms) — CWE-22 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `extension`
Patched: `5.9.13` — 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
**Path traversal** (CWE-22) exists in craftcms/cms. Attackers reach the vulnerable code path via ``extension`` without authentication.
📍 Affected scope
craftcms/cms — . Attack surface: `extension`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.9.13**.
🛡️ 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 'craftcms/cms' .` 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 'craftcms/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `craftcms/cms` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade craftcms/cms to 5.9.13ステージング環境で 5.9.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
craftcms/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.13"}]}]
References
- web https://github.com/craftcms/cms/commit/30f5f1a8d6edf0f3a00be72c42c78d9dc7d72d5c
- web https://github.com/craftcms/cms/security/advisories/GHSA-c43v-4cr8-6mvp
- web https://www.vulncheck.com/advisories/craft-cms-authenticated-path-traversal-in-assets-icon-extension-parameter
- web https://nvd.nist.gov/vuln/detail/CVE-2026-56394
- web https://github.com/advisories/GHSA-jcmp-jxh2-4jc3
- web https://github.com/advisories/GHSA-c43v-4cr8-6mvp