CVE-2026-50283

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
17.9%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Unauthorized Deletion of Source Assets During File Replacement · Advisory · craftcms/cms · GitHub

https://github.com/craftcms/cms/security/advisories/GHSA-qh45-9g5p-m2v4
github_commit Patch Available

commit 2c2579c7f103 (craftcms/cms)

Patch available: craftcms/cms 5.9.21 (contains commit 2c2579c7f103)

https://github.com/craftcms/cms/commit/2c2579c7f1030872423f268d0c8b48377101961d

Vendor Advisories for CVE-2026-50283(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 10× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 10:24 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-05 08:08 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 05:55 UTCEG score recompute
  8. 2026-07-03 03:41 UTCEG score recompute
  9. 2026-07-02 01:22 UTCEG score recompute
  10. 2026-07-02 01:21 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50283?
CVE-2026-50283 is a medium vulnerability published on July 1, 2026. 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.…
When was CVE-2026-50283 disclosed?
CVE-2026-50283 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50283 actively exploited?
CVE-2026-50283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50283?
CVE-2026-50283 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-50283?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50283, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50283

Explore →

Is Your Infrastructure Affected by CVE-2026-50283?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs