# CVE-2025-23209: Craft CMS Code Injection

> Attackers with a compromised security key can achieve remote code execution in Craft CMS installations.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 Feb 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Jan 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-x684-96hh-833x

## What is CVE-2025-23209?

CVE-2025-23209 is a high-severity code injection vulnerability in Craftcms Craft Cms, published on 18 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. This is an remote code execution (RCE) vulnerability that affects Craft 4 and 5 installs where your security key has already been compromised. Anyone running an unpatched version of Craft with a compromised security key is affected. This vulnerability has been patched in Craft 5.5.8 and 4.13.8. Users who cannot update to a patched version, should rotate their security keys and ensure their privacy to help migitgate the issue.

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

## Which versions are affected by CVE-2025-23209?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.13.8 |
| `craftcms/cms` | Packagist | From 4.0.0-RC1 | 4.13.8 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.5.8 |
| `craftcms/cms` | Packagist | From 5.0.0-RC1 | 5.5.8 |

Products: Craftcms Craft Cms.

## How do I fix CVE-2025-23209?

Upgrade craftcms/cms to a fixed version for your release line: 4.13.8 or 5.5.8. US federal agencies must fix it by 13 Mar 2025.

## Is CVE-2025-23209 being exploited?

Yes. Attackers have exploited CVE-2025-23209 in the wild since at least 20 Feb 2025.

## 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-2024-56145](https://insights.sbomify.com/CVE-2024-56145/): Craft CMS Code Injection (critical 9.3, 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-2025-23209 and fix it if it is affected.

What it is: CVE-2025-23209 is a high-severity code injection vulnerability in Craftcms Craft Cms, published on 18 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2025-23209 in the wild since at least 20 Feb 2025.

Affected packages and fixed versions:
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.13.8
- craftcms/cms (Packagist): affected from 4.0.0-RC1; fixed in 4.13.8
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.5.8
- craftcms/cms (Packagist): affected from 5.0.0-RC1; fixed in 5.5.8

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-2025-23209/ (Markdown: https://insights.sbomify.com/CVE-2025-23209/index.md)
```

## Sources

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

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