CVE-2025-32432
KEVCraft CMS Code Injection Vulnerability
Description
Craft CMS contains a code injection vulnerability that allows a remote attacker to execute arbitrary code.
Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. Starting from version 3.0.0-RC1 to before 3.9.15, 4.0.0-RC1 to before 4.14.15, and 5.0.0-RC1 to before 5.6.17, Craft is vulnerable to remote code execution. This is a high-impact, low-complexity attack vector. This issue has been patched in versions 3.9.15, 4.14.15, and 5.6.17, and is an additional fix for CVE-2023-41892.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:LPublishedApr 25, 2025
Last modifiedSep 24, 2026
Added to KEVMar 20, 2026
Remediation dueApr 3, 2026
References
- github.com/craftcms/cms/blob/3.x/CHANGELOG.mdProductRelease Notes
- github.com/craftcms/cms/blob/4.x/CHANGELOG.mdProductRelease Notes
- github.com/craftcms/cms/blob/5.x/CHANGELOG.mdProductRelease Notes
- github.com/craftcms/cms/commit/e1c85441fa47eeb7c688c2053f25419bc0547b47Patch
- github.com/craftcms/cms/security/advisories/GHSA-f3gw-9ww9-jmc3Vendor Advisory
- sensepost.com/blog/2025/investigating-an-in-the-wild-campaign-using-rce-in-craftcms/ExploitPress/Media Coverage
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-32432US Government Resource
0 recent articles mention this CVE
90
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 206 days
- CVSS
- 10.0 CRITICAL
- EPSS (30-day exploit probability)
- 99.8% · top 1% of all CVEs
- Weakness
- CWE-94
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.