Summary
Craft CMS has a theoretical bypass for CVE-2025-23209
Pre-requisites:
- Have a compromised security key (https://craftcms.com/knowledge-base/securing-craft#keep-your-secrets-secret)
- Somehow, manage to create an arbitrary file in Craft’s
/storage/backupsfolder.
With those two pieces in place, you could create a specific, malicious request to the /updater/restore-db endpoint to execute CLI commands remotely.
Fixed in https://github.com/craftcms/cms/commit/a19d46be78a9ca1ea474012a10e97bed0d787f57
Reported by Marco O. (segfault)
Impact
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
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
craftcms/cms to 4.16.3 or later; craftcms/cms to 5.8.4 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-54417? CVE-2025-54417 is a medium-severity code injection vulnerability in craftcms/cms (composer), affecting versions >= 4.13.8, < 4.16.3. It is fixed in 4.16.3, 5.8.4. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of craftcms/cms are affected by CVE-2025-54417? craftcms/cms (composer) versions >= 4.13.8, < 4.16.3 is affected.
- Is there a fix for CVE-2025-54417? Yes. CVE-2025-54417 is fixed in 4.16.3, 5.8.4. Upgrade to this version or later.
- Is CVE-2025-54417 exploitable, and should I be worried? Whether CVE-2025-54417 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-2025-54417 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-2025-54417?
- Upgrade
craftcms/cmsto 4.16.3 or later - Upgrade
craftcms/cmsto 5.8.4 or later
- Upgrade