CVE-2026-50283Craft CMS: Unauthorized Deletion of Source Assets During File Replacement

Official description

Craft CMS is a content management system (CMS). Versions 5.0.0-RC1 through 5.9.20, and 4.0.0-RC1 through 4.17.13 contain an authorization issue in the AssetsController::actionReplaceFile that can delete a source asset without source delete permission by supplying both assetId and sourceAssetId. AssetsController::actionReplaceFile() supports replacing a target asset file using another existing asset as the source. The action loads: assetId -> $assetToReplace and sourceAssetId -> $sourceAsset, then enforces replace permissions using ($assetToReplace ?: $sourceAsset). When both IDs are provided, this expression resolves to the target asset so no permission check is performed against the source asset volume. When both assets are present, Craft copies the source file into the target and then deletes the source asset. There is no deletion check for for the source asset. An authenticated user who can replace files in one volume can delete assets in another volume where they do not have delete permission, as long as they can obtain a sourceAssetId, leading to broken content references and data loss. This issue has been fixed in versions 4.17.14 and 5.9.21.

Affected packages & fixed versions

Affected products (as reported)

References

• https://github.com/craftcms/cms/security/advisories/GHSA-qh45-9g5p-m2v4 x_refsource_CONFIRM
• https://github.com/craftcms/cms/commit/2c2579c7f1030872423f268d0c8b48377101961d x_refsource_MISC