CVE-2026-92592: Craft CMS before 4.18.6 Remote Code Execution via signed cookie
Craft CMS 4.8.0 through 4.18.5 and 5.0.0 through 5.10.12 sign an authenticated user's attacker-controlled license-shun cookie with the same key and format used to validate signed redirect parameters, because the HMAC signature is not bound to its purpose (Yii's cookieValidationKey is derived from the same Craft securityKey used for signed request parameters). An authenticated, non-administrator user (Control Panel access is not required) can set the cookie via the license-shun endpoint and transplant the signed envelope into the redirect parameter; on a successful login, Craft validates the signature and renders the authenticated bytes as an unsandboxed Twig template, where Twig's map filter accepts a string callback and allows PHP system() to execute arbitrary operating-system commands as the web-server user. Exploitation requires an account using password authentication without active 2FA, the default request configuration, and availability of PHP system(). The issue is fixed in 4.18.6 and 5.10.13.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Craft CMSto a version that resolves this vulnerability.Fixed in 4.18.6 - Upgrade
Upgrade
Craft CMSto a version that resolves this vulnerability.Fixed in 5.10.13
Event History
Frequently Asked Questions
Which deployments are exposed to exploitation?
Craft CMS versions 4.8.0 through 4.18.5 and 5.0.0 through 5.10.12 are affected. Exploitation also depends on the default request configuration and PHP's system() function being available.
What level of access does an attacker need?
An attacker needs a valid non-administrator account that uses password authentication and does not have active 2FA. Control Panel access is not required.
What is the practical impact of successful exploitation?
A successful attacker can execute arbitrary operating-system commands as the web-server user. This can affect confidentiality, integrity, and availability.
What versions contain the fix?
Upgrade Craft CMS to version 4.18.6 or later on the 4.x branch, or 5.10.13 or later on the 5.x branch.