Security readout for executives and security teams
Plain-English summary
CVE-2025-23209 is a high-severity Craft CMS issue that can allow remote code execution if an attacker already has the site's security key. CISA lists it in the Known Exploited Vulnerabilities catalog, so internet-facing Craft sites should be treated as urgent, especially where secrets may have leaked.
Executive priority
Prioritize remediation for internet-facing Craft CMS sites this cycle. KEV listing raises urgency, but scope depends on whether the Craft security key was exposed or plausibly compromised.
Technical view
The issue affects Craft CMS 4 and 5 and is categorized as CWE-94 code injection. The CVSS is 8.1 with network attack vector, high complexity, low privileges, user interaction, and changed scope. Sources state patched releases are Craft 5.5.8 and 4.13.8; one affected-version entry conflicts on the Craft 5 cutoff.
Likely exposure
Exposure is most likely for Craft CMS 4 or 5 deployments below patched releases, especially public sites with reused, leaked, committed, logged, or otherwise compromised security keys.
Exploitation context
CISA KEV status supports known exploitation. Public source details indicate exploitation requires a compromised security key, so this is not described as a simple unauthenticated RCE in the supplied evidence.
Researcher notes
Do not assume all Craft sites are exploitable. Validate version, key secrecy, and deployment history. The supplied sources disagree on the Craft 5 affected cutoff, so use the GitHub advisory and vendor release guidance when confirming remediation.
Mitigation direction
- Upgrade Craft CMS to 5.5.8, 4.13.8, or later vendor-fixed releases.
- Rotate Craft security keys if compromise is possible or cannot be ruled out.
- Review repositories, backups, logs, and deployment systems for exposed security keys.
- Restrict and audit access to environment variables and secret stores.
- Follow Craft's guidance for keeping secrets private.
Validation and detection
- Inventory all Craft CMS 4 and 5 installations and record exact versions.
- Confirm whether each instance is at or above the vendor-fixed release.
- Check secret exposure history in source control, CI logs, backups, and support bundles.
- Review web, application, and admin logs for suspicious activity around the disclosure window.
- Confirm rotated keys are deployed consistently across all environments.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-23209 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H1.36Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/craftcms/cms/security/advisories/GHSA-x684-96hh-833xCVE reference · x_refsource_CONFIRM
- https://github.com/craftcms/cms/commit/e59e22b30c9dd39e5e2c7fe02c147bcbd004e603CVE reference · x_refsource_MISC
- https://craftcms.com/knowledge-base/securing-craft#keep-your-secrets-secretCVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-23209CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.