Categories
CVE-2026-44012

Vulnerability in craftcms/cms (CVE-2026-44012)

Summary

Vulnerability in craftcms/cms (CVE-2026-44012). Risk of unauthorized operations or information disclosure. Exploitable via viewAssets. Mitigation: upgrade to 5.9.18 or later.

Original description

The description as published by the source.

Craft CMS is a content management system (CMS). From 5.0.0-RC1 to before 5.9.18, AssetsController::actionShowInFolder() fetches an asset by ID and returns its filename and complete folder hierarchy (including volume handle, volume UID, folder names, folder UIDs, and folder URI paths) without checking whether the requesting user has viewAssets or viewPeerAssets permission on the asset’s volume. Any authenticated CP user — even one with zero volume permissions — can enumerate asset filenames and the full folder structure of any volume by supplying arbitrary asset IDs. This vulnerability is fixed in 5.9.18.

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-44012 has been found in craftcms/cms.
Attackers can target a specific entry point like viewAssets over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade craftcms/cms to 5.9.18 or later.
If unsure, ask your IT team or search "craftcms/cms CVE-2026-44012" on the vendor's site.

CVE-2026-44012 (craftcms/cms) — CWE-862
Attack surface: viewAssets / viewPeerAssets / actionShowInFolder / accessCp
Patched: 5.9.18 — 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

A vulnerability (CWE-862) exists in craftcms/cms. Attackers reach the vulnerable code path via viewAssets.

📍 Affected scope

Check the vendor advisory for the affected versions of craftcms/cms. Attack surface: viewAssets / viewPeerAssets / actionShowInFolder / accessCp.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.9.18.

🛡️ 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

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

  1. 1
    Identify exposure identify
    grep -r 'craftcms/cms' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade craftcms/cms to 5.9.18

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

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

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

Affected packages

composer craftcms/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.18"}]}]
Packagist craftcms/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0-RC1"},{"fixed":"5.9.18"}]}]

References

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