Code Injection in Craft CMS (CVE-2026-92593)
Summary
Code injection in Craft CMS (CVE-2026-92593). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.10.13 or later.
Original description
The description as published by the source.
Craft CMS versions 5.10.0 through 5.10.12 contain an incomplete fix for CVE-2026-55794: the Controller::getPostedRedirectUrl() -> View::renderObjectTemplate() sink remained unsandboxed, and the same fix commit added a self-signing oracle in Cp::elementLabelHtml(). Because Craft/Yii HMAC tokens are not bound to a parameter name, an authenticated low-privilege control panel user with edit rights on a single element type can mint a token over attacker-controlled Twig for the returnUrl parameter and replay it as the redirect POST parameter, reaching the unsandboxed sink and achieving server-side template injection that executes arbitrary PHP code (full server compromise). The issue is fixed in 5.10.13.
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-92593 has been found in Craft CMS.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade Craft CMS to 5.10.13 or later.
If unsure, ask your IT team or search "Craft CMS CVE-2026-92593" on the vendor's site.
CVE-2026-92593 (Craft CMS) — CWE-94 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.10.13 — 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.
Arbitrary code execution (CWE-94) exists in Craft CMS.
Check the vendor advisory for the affected versions of Craft CMS.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 5.10.13.
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. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Craft CMS を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade Craft CMS to 5.10.13ステージング環境で 5.10.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- web github.com