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:
- Calls
requireCpRequest() — verifies the request targets the CP, enforces accessCp permission via Controller::_enforceAllowAnonymous(), but does NOT enforce any volume-level permission.
- Fetches any asset by ID with
Asset::findOne($assetId) — no editable/savable scope filter, so all assets across all volumes are reachable.
- Returns sensitive structural data via JSON.
Impact
- Any authenticated control panel user with only
accessCp permission 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.
References
e3f3eaa
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 hasviewAssetsorviewPeerAssetspermission 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. TheactionShowInFoldermethod was introduced thirteen days before the patch wave and was not included in it.Details
The vulnerability is in
src/controllers/AssetsController.phpat line 1437. The method:requireCpRequest()— verifies the request targets the CP, enforcesaccessCppermission viaController::_enforceAllowAnonymous(), but does NOT enforce any volume-level permission.Asset::findOne($assetId)— noeditable/savablescope filter, so all assets across all volumes are reachable.Impact
accessCppermission can discover the filenames and complete folder structure (names, UIDs, handles, URIs) of assets in volumes they are not authorized to access.References
e3f3eaa