Craft CMS up to 4.17.14/5.9.21 Sibling actionDeleteAsset Endpoint actionDeleteFolder authorization

Summaryinfo

A vulnerability marked as problematic has been reported in Craft CMS up to 4.17.14/5.9.21. This vulnerability affects the function theAssetsController::actionDeleteFolder of the component Sibling actionDeleteAsset Endpoint. The manipulation leads to authorization. This vulnerability is referenced as CVE-2026-50284. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Craft CMS up to 4.17.14/5.9.21. It has been rated as problematic. This issue affects the function theAssetsController::actionDeleteFolder of the component Sibling actionDeleteAsset Endpoint. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity. The summary by CVE is:

Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.21 and 4.0.0-RC1 through 4.17.14, theAssetsController::actionDeleteFolder() only requires the deleteAssets: permission for the target folder. It never enforces deletePeerAssets:, even though Assets::deleteFoldersByIds() cascades deletion to every descendant folder and every asset inside, regardless of the uploader's assigned privileges. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling actionDeleteAsset endpoint correctly applies. This issue has been fixed in versions 4.17.15 and 5.9.22.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-50284 since 06/04/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

Upgrading to version 4.17.15 or 5.9.22 eliminates this vulnerability. Applying the patch b4e08977f0c9bdf002a77f9f6d1346cd55ac0598 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Craft

Name

• CMS

Version

• 4.17.0
• 4.17.1
• 4.17.2
• 4.17.3
• 4.17.4
• 4.17.5
• 4.17.6
• 4.17.7
• 4.17.8
• 4.17.9
• 4.17.10
• 4.17.11
• 4.17.12
• 4.17.13
• 4.17.14
• 5.9.0
• 5.9.1
• 5.9.2
• 5.9.3
• 5.9.4
• 5.9.5
• 5.9.6
• 5.9.7
• 5.9.8
• 5.9.9
• 5.9.10
• 5.9.11
• 5.9.12
• 5.9.13
• 5.9.14
• 5.9.15
• 5.9.16
• 5.9.17
• 5.9.18
• 5.9.19
• 5.9.20
• 5.9.21

License

• free

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion