CVE-2025-23209
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Code injection payloads are often obfuscated, so they slip past generic WAF rules.
Also consider: remove eval sinks · RASP
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-23209 being exploited?
Yes. CVE-2025-23209 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-23209?
CVE-2025-23209 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-23209?
Yes. A fix has been recorded for CVE-2025-23209. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-23209 affect?
CVE-2025-23209 affects craftcms:craft_cms. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 5.0.0-RC1 and < 5.5.5
- affected>= 4.0.0-RC1 and < 4.13.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 21 Feb 2025 (SSVC 2.0.3).
timeline
- 18 Jan 2025Published
- 20 Feb 2025Added to CISA KEV (exploited in the wild) · 33 days later
- 21 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 13 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 26 Feb 2026CVE record last updated · 351 days (about 12 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
also known as
- Linkgithub.com /craftcms/cms/security/advisories/GHSA-x684-96hh-833x
- Linkgithub.com /craftcms/cms/commit/e59e22b30c9dd39e5e2c7fe02c147bcbd004e603
- Linkcraftcms.com /knowledge-base/securing-craft#keep-your-secrets-secret
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-23209
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.