Threats / Craft CMS / CVE-2025-32432
CVE-2025-32432
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Craft CMS vulnerability
Craft CMS contains a code injection vulnerability (CWE-94) allowing remote attackers to execute arbitrary code. The vulnerability is actively exploited in the wild.
Verdict
Today item — known-exploited.
A remote code injection flaw in Craft CMS enables unauthenticated attackers to achieve arbitrary code execution on affected systems. Active exploitation in the wild poses immediate risk to deployed instances.
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
10 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 2026-03-20).
Probability (EPSS)
EPSS 0.99734 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Craft CMS, Craft CMS. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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 identify a code injection point in Craft CMS that accepts unsanitized input.
Business
Attackers gain the ability to execute arbitrary code with the privileges of the web server process.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious payload and send it to the vulnerable endpoint to trigger code execution.
Business
The organization's server is compromised, allowing attackers to read, modify, or delete sensitive data.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence by installing backdoors or web shells on the compromised system.
Business
Attackers maintain long-term access to critical infrastructure and customer data.
4
Data at risk — exfiltration narrative 4
Attacker
I pivot to internal systems or exfiltrate databases containing customer information.
Business
The organization faces data breach liability, regulatory fines, 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