Vulnerability in craftcms/cms (CVE-2026-50284)
Summary
Vulnerability in craftcms/cms (CVE-2026-50284). Risk of unauthorized operations or information disclosure. Exploitable via actionDeleteAsset. Mitigation: upgrade to 4.17.15 or later.
Original description
The description as published by the source.
Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.21 and 4.0.0-RC1 through 4.17.14, theAssetsController::actionDeleteFolder() only requires the deleteAssets: permission for the target folder. It never enforces deletePeerAssets:, even though Assets::deleteFoldersByIds() cascades deletion to every descendant folder and every asset inside, regardless of the uploader's assigned privileges. A low-privilege user who has been granted folder-management rights on a shared volume can therefore destroy assets uploaded by other users (peer assets), bypassing the per-asset peer-permission check that the sibling actionDeleteAsset endpoint correctly applies. This issue has been fixed in versions 4.17.15 and 5.9.22.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50284 has been found in craftcms/cms.
Attackers can target a specific entry point like actionDeleteAsset over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade craftcms/cms to 4.17.15 or later.
If unsure, ask your IT team or search "craftcms/cms CVE-2026-50284" on the vendor's site.
CVE-2026-50284 (craftcms/cms) — CWE-862
Attack surface: actionDeleteAsset / actionMoveFolder / savePeerAssets / requirePeerVolumePermissionByAsset
Patched: 4.17.15 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in craftcms/cms. Attackers reach the vulnerable code path via actionDeleteAsset.
Check the vendor advisory for the affected versions of craftcms/cms. Attack surface: actionDeleteAsset / actionMoveFolder / savePeerAssets / requirePeerVolumePermissionByAsset.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.17.15.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'craftcms/cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'craftcms/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
craftcms/cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade craftcms/cms to 4.17.15ステージング環境で 4.17.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com