dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Apr 2026.
Craft CmsApplication · Craftcms

CVE-2025-32432

CRITICAL · 10.0 CVSS v3.1 Published 2025-04-25
Fix available
A fix is available. Upgrade to 3.9.15 / 4.14.15 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Craft CMS contains a remote code execution vulnerability affecting versions 3.0.0-RC1 through 3.9.14, 4.0.0-RC1 through 4.14.14, and 5.0.0-RC1 through 5.6.16. This is an additional fix for CVE-2023-41892, indicating a bypass or incomplete remediation of the prior RCE vulnerability, with low attack complexity and critical severity.

MitigationUpgrade Craft CMS to version 3.9.15, 4.14.15, or 5.6.17 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Craft CmsApplication
Affected:>= 3.0.0, < 3.9.15>= 4.0.0, < 4.14.15>= 5.0.0, < 5.6.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Craft CMS version file
    Check the composer.json file in the web root, or look for a version.php file in the craft/app/ directory (v3) or vendor/craftcms/cms/ (v4/v5)
    Affected if The installed version falls within the affected ranges: 3.0.0 to 3.9.14, 4.0.0 to 4.14.14, or 5.0.0 to 5.6.16
  2. Check admin panel version display
    Log into the Craft CMS control panel and navigate to Utilities > System Report, or check the footer of the admin dashboard for the version number
    Affected if The displayed version is less than 3.9.15 (for v3), less than 4.14.15 (for v4), or less than 5.6.17 (for v5)
  3. Query installed package version via Composer
    Run `composer show craftcms/cms` in the project directory to display the installed version details
    Affected if The installed version matches the affected version ranges listed in the CVE

If your Craft CMS installation version is 3.9.14 or lower, 4.14.14 or lower, or 5.6.16 or lower, you are running a vulnerable version and should treat this as a critical priority.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.9.15 / 4.14.15 / 5.6.17 or later
Fixed in 3.9.154.14.155.6.17
Vendor patch github.com →
Interim mitigation

Upgrade Craft CMS to version 3.9.15, 4.14.15, or 5.6.17 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to 3.9.15 (for 3.x), 4.14.15 (for 4.x), or 5.6.17 (for 5.x) depending on your current major version

  1. 1. Back up your entire Craft CMS installation including the database before proceeding
  2. 2. Identify your current Craft CMS version by checking the composer.json file or the admin panel
  3. 3. For Craft CMS 3.x users: Run `composer require craftcms/cms:^3.9.15 --no-interaction` to upgrade to version 3.9.15
  4. 4. For Craft CMS 4.x users: Run `composer require craftcms/cms:^4.14.15 --no-interaction` to upgrade to version 4.14.15
  5. 5. For Craft CMS 5.x users: Run `composer require craftcms/cms:^5.6.17 --no-interaction` to upgrade to version 5.6.17
  6. 6. Run `composer update --no-interaction` to apply the changes
  7. 7. Clear any application caches after the upgrade
  8. 8. Verify the upgrade was successful by checking the admin panel and testing critical functionality
Caveat Minor version upgrades within the same major version (e.g., 3.x to 3.9.15) typically have minimal breaking changes, but test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Craft Cms Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32432 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32432 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data