Quick answers
- Is CVE-2025-32432 exploited in the wild?
- Yes. CVE-2025-32432 is known to be exploited in the wild, first recorded on 20 March 2026. Treat it as urgent.
- How severe is CVE-2025-32432?
- Critical severity, with a CVSS score of 3.1, published 25 April 2025.
- Which products and versions are affected?
- craftcms/cms (Packagist) ECOSYSTEM:introduced=3.0.0-RC1,fixed=3.9.15.
- Is there a fix for CVE-2025-32432?
- Yes. craftcms/cms (Packagist): upgrade to 3.9.15 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-32432 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-32432?
- Check whether you run Craft CMS or craftcms/cms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- craftcms/cms (Packagist): upgrade to 3.9.15 or later
composer require craftcms/cms:^3.9.15
Technical details
Craft CMS is vulnerable to remote code execution (RCE) due to improper control of code generation (CWE-94). The vulnerability allows a remote, unauthenticated attacker to inject and execute arbitrary code on the underlying server with high impact and low complexity. This issue is noted as an additional fix for the previous CVE-2023-41892. CISA has confirmed active exploitation in the wild. Patches are available in versions 3.9.15, 4.14.15, and 5.6.17.
Affected products
- Craft CMS Craft CMS 3.0.0-RC1 to < 3.9.15, 4.0.0-RC1 to < 4.14.15, 5.0.0-RC1 to < 5.6.17
Identifiers
- CVE-2025-32432
- GHSA-f3gw-9ww9-jmc3
Timeline
- 2025-04-10: patched: Vendor released patches across major versions 3.x, 4.x, and 5.x.
- 2025-04-25: disclosed: Initial CVE publication.
- 2026-03-20: kev added: CISA added the vulnerability to the Known Exploited Vulnerabilities (KEV) catalog.