Craft CMS's Missing Volume Permission Check in AssetsController::actionShowInFolder Allows Information Disclosure
Published 6 May 2026 · Updated 13 May 2026
Is your project on an affected craftcms/cms?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=5.0.0-RC1 <5.9.18
- Fixed in
- 5.9.18
composer require craftcms/cms:^5.9.18Details
Summary
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 follows the exact same incomplete-patch pattern as four GHSAs merged on 2026-02-25 (GHSA-x76w-8c62-48mg, GHSA-vgjg-248p-rfm2, GHSA-5pgf-h923-m958, GHSA-3pvf-vxrv-hh9c), all of which added requireVolumePermissionByAsset() + requirePeerVolumePermissionByAsset() to sibling AssetsController actions. The actionShowInFolder method was introduced thirteen days before the patch wave and was not included in it.
Details
The vulnerability is in src/controllers/AssetsController.php at line 1437. The method:
1. Calls requireCpRequest() — verifies the request targets the CP, enforces accessCp permission via Controller::_enforceAllowAnonymous(), but does NOT enforce any volume-level permission.
2. Fetches any asset by ID with Asset::findOne($assetId) — no editable/savable scope filter, so all assets across all volumes are reachable.
3. Returns sensitive structural data via JSON.
Impact
- Any authenticated control panel user with only
accessCppermission can discover the filenames and complete folder structure (names, UIDs, handles, URIs) of assets in volumes they are not authorized to access. - Sensitive volume structures — private document repositories, confidential media, internal file names — are exposed to any user who can log into the control panel.
- This enables targeted follow-up attacks: an attacker who knows a private asset’s filename and folder path may have other avenues to exfiltrate the actual file.
Resources
https://github.com/craftcms/cms/commit/e3f3eaab3d85badd713cfc2c24e5f0792ecdb586
Is GHSA-33m5-hqp9-97pw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected craftcms/cms, and gives you the command that fixes it.
More advisories for craftcms/cms
- CriticalCVE-2026-72780Craft CMS: Passkey login accepts replayed WebAuthn assertions · 7 Aug 2026
- MediumCVE-2026-72779Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts · 6 Aug 2026
- MediumCVE-2026-72782Craft CMS: Authenticated leak of secret environment variables · 6 Aug 2026
- MediumCVE-2026-72785Craft CMS: Authorization bypass: view-only Categories user can modify category structure via structures/move-element · 6 Aug 2026
- MediumCVE-2026-14794Craft CMS: Missing authorization check allows non-admin control panel users access to user registration metrics · 6 Aug 2026
- LowCVE-2026-72783Craft CMS: Incorrect path validation could potentially lead to path traversal · 6 Aug 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.