Is CVE-2026-50283 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50283 being exploited in the wild.

How severe is CVE-2026-50283?

Medium severity, with a CVSS score of 4, published 1 July 2026.

Which products and versions are affected?

craftcms/cms (Packagist) ECOSYSTEM:introduced=5.0.0-RC1,fixed=5.9.21.

Is there a fix for CVE-2026-50283?

Yes. craftcms/cms (Packagist): upgrade to 5.9.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50283 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-50283?

Check whether you run craftcms/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50283: Craft CMS unauthorized asset deletion in AssetsController

CVE-2026-50283 · Severity: medium · CVSS 4 · Published 2026-07-01

Craft CMS, a popular content management system, contains a flaw that allows certain authorized users to delete files they shouldn't have access to. Specifically, a user with permission to replace files in one area can trick the system into deleting files in a different, restricted area. This could lead to data loss, broken website links, and unauthorized removal of important digital assets.

Technologies: craftcms/cms (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-50283 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50283 being exploited in the wild.
How severe is CVE-2026-50283?: Medium severity, with a CVSS score of 4, published 1 July 2026.
Which products and versions are affected?: craftcms/cms (Packagist) ECOSYSTEM:introduced=5.0.0-RC1,fixed=5.9.21.
Is there a fix for CVE-2026-50283?: Yes. craftcms/cms (Packagist): upgrade to 5.9.21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50283 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-50283?: Check whether you run craftcms/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

craftcms/cms (Packagist): upgrade to 5.9.21 or later
```
composer require craftcms/cms:^5.9.21
```

Technical details

An authorization bypass exists in Craft CMS's `AssetsController::actionReplaceFile()` due to improper permission validation when both an `assetId` and `sourceAssetId` are provided. The controller uses a ternary expression `($assetToReplace ?: $sourceAsset)` to check permissions; when both IDs are present, it only validates the 'replace' permission for the target asset and fails to verify 'delete' permissions for the source asset. Consequently, the application copies the source file to the target and then invokes `deleteElement()` on the source asset. An authenticated attacker with file replacement privileges in any volume can exploit this to delete assets in other volumes, provided they know the target asset's ID. This issue is patched in versions 4.17.14 and 5.9.21.

Affected products

Pixel & Tonic Craft CMS >= 4.0.0-RC1, < 4.17.14; >= 5.0.0-RC1, < 5.9.21

Identifiers

CVE-2026-50283
GHSA-qh45-9g5p-m2v4

Timeline

2026-05-29: disclosed: Initial disclosure to vendor
2026-07-01: advisory: NVD publication date
2026-07-02: patched: GitHub Advisory published and versions patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.