Advisory

GHSA-qh45-9g5p-m2v4

Also known as: CVE-2026-50283

Summary

Craft CMS: Unauthorized Deletion of Source Assets During File Replacement

Details

We have identified an authorization issue in Craft CMS AssetsController::actionReplaceFile that can delete a source asset without source delete permission by supplying both assetId and sourceAssetId.

Description

Craft CMS’s craft\\controllers\\AssetsController::actionReplaceFile() supports replacing a target asset file using another existing asset as the source. The action loads:

  • $assetToReplace from assetId
  • $sourceAsset from sourceAssetId

It 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.

$this->requireVolumePermissionByAsset('replaceFiles', $assetToReplace ?: $sourceAsset);
$this->requirePeerVolumePermissionByAsset('replacePeerFiles', $assetToReplace ?: $sourceAsset);

*src/controllers/AssetsController.php:L433-L434*

In the branch where both assets are present, Craft copies the source file into the target and then deletes the source asset. There is no check for deleteAssets:<sourceVolumeUid> or deletePeerAssets:<sourceVolumeUid> for the source asset before deletion.

$assets->replaceAssetFile($assetToReplace, $tempPath, $assetToReplace->getFilename(), $sourceAsset->getMimeType());
Craft::$app->getElements()->deleteElement($sourceAsset);

*src/controllers/AssetsController.php:L462-L463*

Impact

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. This can lead to unauthorized asset deletion, broken content references, and data loss.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-07-02 18:48 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

craftcms/cms

Packagist · All systems

Affected

  • introduced 5.0.0-RC1, fixed 5.9.21 (ecosystem)

Fixed versions

5.9.21

Fix

The export has no generic command for this ecosystem.

craftcms/cms

Packagist · All systems

Affected

  • introduced 4.0.0-RC1, fixed 4.17.14 (ecosystem)

Fixed versions

4.17.14

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences