Threats / Craft CMS / CVE-2024-56145
CVE-2024-56145
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Craft CMS vulnerability
Craft CMS contains a code injection vulnerability (CWE-94) enabling remote code execution when php.ini register_argc_argv is enabled. Actively exploited in the wild with high EPSS score.
Verdict
Today item — known-exploited.
A code injection flaw in Craft CMS allows unauthenticated remote code execution under specific PHP configurations. The vulnerability is being actively exploited and poses critical risk to affected deployments, particularly those with register_argc_argv enabled.
CISA KEV Yes · 2025-06-025EPSS 0.97446 (verify live)6Exploit Weaponized · public PoC7CVSS 9.33CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
9 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-02).
Probability (EPSS)
EPSS 0.97446 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 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) · Affected: Craft CMS, Craft CMS. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 166 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request that injects code into Craft CMS application logic.
Business
Attackers gain arbitrary code execution capability on the web server.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute system commands and establish persistent access to the compromised server.
Business
Full server compromise enables data theft, lateral movement, and infrastructure takeover.
3
Lateral reach — past segmentation narrative 3
Attacker
I exfiltrate sensitive data including database credentials, user information, and application secrets.
Business
Confidential business data and customer information are exposed, triggering compliance violations and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05