Summary
Craft CMS Remote Code Execution vulnerability
Mitigations
- This has been fixed in Craft 4.4.15. You should ensure you’re running at least that version.
- Refresh your security key in case it has already been captured. You can do that by running the
php craft setup/security-keycommand and copying the updatedCRAFT_SECURITY_KEYenvironment variable to all production environments. - If you have any other private keys stored as environment variables (e.g., S3 or Stripe), refresh those as well.
- Out of an abundance of caution, you may want to force all your users to reset their passwords in case your database was compromised. You can do that by running
php craft resave/users --set passwordResetRequired --to "fn() => true".
References
https://github.com/craftcms/cms/commit/7359d18d46389ffac86c2af1e0cd59e37c298857
https://github.com/craftcms/cms/commit/a270b928f3d34ad3bd953b81c304424edd57355e
https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4415---2023-07-03-critical
Impact
This is a high-impact, low-complexity attack vector. Users running Craft installations before 4.4.15 are encouraged to update to at least that version to mitigate the issue.
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
CVE-2023-41892 has a CVSS score of 10.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.4.15); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2023-41892? CVE-2023-41892 is a critical-severity code injection vulnerability in craftcms/cms (composer), affecting versions >= 4.0.0-RC1, <= 4.4.14. It is fixed in 4.4.15. Untrusted input is evaluated as executable code within the application's runtime environment.
- How severe is CVE-2023-41892? CVE-2023-41892 has a CVSS score of 10.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of craftcms/cms are affected by CVE-2023-41892? craftcms/cms (composer) versions >= 4.0.0-RC1, <= 4.4.14 is affected.
- Is there a fix for CVE-2023-41892? Yes. CVE-2023-41892 is fixed in 4.4.15. Upgrade to this version or later.
- Is CVE-2023-41892 exploitable, and should I be worried? Whether CVE-2023-41892 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-41892 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-41892? Upgrade
craftcms/cmsto 4.4.15 or later.