# CVE-2024-56145: Craft CMS Code Injection

> Remote code execution is possible in Craft CMS when the PHP register_argc_argv setting is enabled, requiring an upgrade or configuration change.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 2 Jun 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Dec 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-2p6p-9rc9-62j9

## What is CVE-2024-56145?

CVE-2024-56145 is a critical code injection vulnerability in Craftcms Craft Cms, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. Users of affected versions are affected by this vulnerability if their php.ini configuration has `register_argc_argv` enabled. For these users an unspecified remote code execution vector is present. Users are advised to update to version 3.9.14, 4.13.2, or 5.5.2. Users unable to upgrade should disable `register_argc_argv` to mitigate the issue.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-56145?

6 open source packages ship an affected version, including craftcms/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 3.0.0 | 3.9.14 |
| `craftcms/cms` | Packagist | From 3.0.0 | 3.9.14 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.13.2 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.13.2 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.5.2 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.5.2 |

Products: Craftcms Craft Cms.

## How do I fix CVE-2024-56145?

Upgrade craftcms/cms to a fixed version for your release line: 3.9.14, 4.13.2 or 5.5.2. US federal agencies must fix it by 23 Jun 2025.

## Is CVE-2024-56145 being exploited?

Yes. Attackers have exploited CVE-2024-56145 in the wild since at least 2 Jun 2025.

Public exploit code:

- Unauthenticated RCE on CraftCMS when PHP `register_argc_argv` config setting is enabled (github_poc): https://github.com/Chocapikk/CVE-2024-56145
- CVE-2024-56145 SSTI to RCE - twig templates  (github_poc): https://github.com/Sachinart/CVE-2024-56145-craftcms-rce
- Craft CMS Twig Template Injection RCE via FTP Templates Path (metasploit)
- A POC lab environment for CVE-2024-56145 CraftCMS RCE. (github_poc): https://github.com/hmhlol/craft-cms-RCE-CVE-2024-56145
- Craft CMS - Remote Code Execution via Template Path Manipulation (nuclei): http/cves/2024/CVE-2024-56145.yaml

## Other vulnerabilities in Craftcms Craft Cms

- [CVE-2025-32432](https://insights.sbomify.com/CVE-2025-32432/): Craft CMS Code Injection (critical 10.0, exploited in the wild)
- [CVE-2025-23209](https://insights.sbomify.com/CVE-2025-23209/): Craft CMS Code Injection (high 8.1, exploited in the wild)
- [CVE-2025-35939](https://insights.sbomify.com/CVE-2025-35939/): Craft CMS External Control of Assumed-Immutable Web Parameter (medium 6.9, exploited in the wild)
- [CVE-2023-41892](https://insights.sbomify.com/CVE-2023-41892/): Craft CMS Remote Code Execution vulnerability (critical 10.0)
- [CVE-2021-27903](https://insights.sbomify.com/CVE-2021-27903/): Craft CMS Remote Code Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56145 and fix it if it is affected.

What it is: CVE-2024-56145 is a critical code injection vulnerability in Craftcms Craft Cms, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-56145 in the wild since at least 2 Jun 2025.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 3.0.0; fixed in 3.9.14
- craftcms/cms (Packagist): affected from 3.0.0; fixed in 3.9.14
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.13.2
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.13.2
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.5.2
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.5.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56145/ (Markdown: https://insights.sbomify.com/CVE-2024-56145/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56145
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56145
- OSV: https://osv.dev/vulnerability/CVE-2024-56145

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56145/
Summaries are generated and may contain mistakes; the official description above is the record.