# CVE-2026-50283 — craftcms cms

> As of 2026-07-02, CVE-2026-50283 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in craftcms cms, CVSS v4.0 5.3, EPSS 0.2% (17.9th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-50283 as of 2026-07-02; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-02

## What is CVE-2026-50283?

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.

The record classifies CVE-2026-50283 under weakness classes [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862), [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639). 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 96 days ago.

## Severity and exploitation probability

- **CVSS v4.0 base score:** 5.3 — Medium (derived from score) (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 17.9% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-01, last modified 2026-07-02

## Is CVE-2026-50283 being exploited?

It currently carries a trending score of 34 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [craftcms](https://intel.threadlinqs.com/vendors/craftcms): cms

## How to fix CVE-2026-50283

No vendor patch reference has been recorded for CVE-2026-50283 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-50283

No threat campaign in the Threadlinqs corpus currently references CVE-2026-50283, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on 2026-07-02.

**Vendor advisory and patch**

- [github.com](https://github.com/craftcms/cms/security/advisories/GHSA-qh45-9g5p-m2v4)

**Other references**

- [github.com](https://github.com/craftcms/cms/commit/2c2579c7f1030872423f268d0c8b48377101961d)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-50283
Full detection coverage and IOCs for threats exploiting CVE-2026-50283 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp