← Back
GHSA-x76w-8c62-48mg
Information Disclosure in craftcms/cms (GHSA-x76w-8c62-48mg)
Summary
vulnerability in craftcms/cms (GHSA-x76w-8c62-48mg). Risk of unauthorized operations or information disclosure. Exploitable via ``assetId``. Mitigation: upgrade to `5.9.14` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-x76w-8c62-48mg** has been found in craftcms/cms.
Attackers can target a specific entry point like ``assetId`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade craftcms/cms to **5.9.14** or later.
If unsure, ask your IT team or search "craftcms/cms GHSA-x76w-8c62-48mg" on the vendor's site.
GHSA-x76w-8c62-48mg (craftcms/cms) — CWE-200 /
Attack surface: `assetId`
Patched: `5.9.14` — 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
**information disclosure** (CWE-200) exists in craftcms/cms. Attackers reach the vulnerable code path via ``assetId`` without authentication.
📍 Affected scope
craftcms/cms — . Attack surface: `assetId`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.9.14**.
🛡️ 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.14ステージング環境で 5.9.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.14"}]}]