Craftcms cms
Control panel only API response emulation replaces "securityKey" and reaches server RCE
The app/process-api-response-headers action accepts fake Craft API response headers from any authenticated control panel user. A non-admin user with only accessCp can place newline characters in X-Craft-Plugin-Licenses. Craft passes this value to its .env writer without removing the newlines. This lets the user insert a new attacker-known CRAFT_SECURITY_KEY into .env. After Craft loads that key, the user can forge a signed login redirect containing a Twig system() callback. This is different from the previous report. That report reads the existing key through a Twig sandbox bypass. This report replaces the key through fake API headers and CRLF injection. Fixing either source does not fix the other.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5.0.0, < 5.11.2
- >= 4.0.0, < 4.18.9
Fixed in 5.11.2, 4.18.9
Mitigation
Upgrade cms to 5.11.2 or 4.18.9 or later.
References
- Mitigation hckrt.com/hacktivity/HCKRT-WM3VSE
- Release notes github.com/craftcms/cms/releases/tag/5.11.2
- Vendor advisory github.com/craftcms/cms/security/advisories/GH…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.