CriticalCVE-2025-32432

    Craft CMS Allows Remote Code Execution (CVE-2025-32432)

    Published Last modified In CISA KEV since Sources: OSV, CVE.org

    Share

    What is affected, what to do

    The vulnerability CVE-2025-32432 allows remote code execution (RCE) in Craft CMS, enabling an attacker to execute arbitrary code. It affects versions from 3.0.0-RC1 to 3.9.14, 4.0.0-RC1 to 4.14.14, and 5.0.0-RC1 to 5.6.16. The issue is actively exploited in the wild and has been patched in versions 3.9.15, 4.14.15, and 5.6.17. Organizations should urgently update to the patched versions to secure their systems.

    The vulnerability is being actively exploited; treat it as a priority. Update craft_cms to version 5.6.17. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • CraftCMS CMS gte 3.0.0-RC1, < 3.9.15..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    10.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    10.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: OSV, CVE.org

    99.79 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.96

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    238.59 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    10.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    10.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.79 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.96
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 28 April 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-94

    Response and mitigation

    Why act now?

    Prioritisation rationale

    The flaw is network-reachable without authentication, trivial to exploit, and gives full code execution with scope change. It sits among the CVEs most likely to be exploited anywhere. Attackers mass-scan for Craft installations, drop web shells, and use the hosts for data theft, harvesting secrets from .env, or as a pivot point. Typical victims are corporate websites, campaign microsites and agency-managed instances that often fall outside central patch management. CISA has not flagged ransomware use, but every internet-facing unpatched instance should still be treated as critical and patched or isolated within 24 h; internal-only deployments are high priority but can follow.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch now: Upgrade every Craft CMS instance to 3.9.15, 4.14.15 or 5.6.17 (or later within the same major line), e.g. via composer update craftcms/cms followed by php craft up. All releases from 3.0.0-RC1 below those versions are affected. Sites that were only patched for CVE-2023-41892 remain vulnerable.
      • Build an inventory: Find every internet-facing Craft deployment, including agency-hosted, staging and campaign microsites. Check the version under Utilities → System Report or in composer.lock.
      • Block if patching slips: At the reverse proxy or WAF, block POST requests to actions/assets/generate-transform, especially when the body contains __class. Cover both the path form and the ?p=admin/actions/assets/generate-transform query form.
      • Hunt for compromise: Search access logs going back several months for POSTs to that endpoint carrying __class. Sweep the webroot (web/) for unexpected .php files such as web shells or file managers.
      • If compromise is suspected:
        • Regenerate the security key with php craft setup/security-key.
        • Rotate database credentials and any API keys or cloud secrets stored in .env.
        • Force password resets for all users.
        • Take a forensic image before rebuilding the host.
      • Check reporting duties: On confirmed compromise, assess your NIS2 reporting obligations. The early warning to the national CSIRT or authority is due within 24 h.

    2. Runbook step 2

      Mitigation layers

      • WAF/IPS: Deny requests that have generate-transform in the URI or p parameter and __class in the body. Also enable generic PHP object-injection signatures, e.g. for body patterns such as GuzzleHttp\\Psr7\\FnStream or yii\\rbac\\PhpManager.
      • Network segmentation: Restrict the control panel (/admin, cpTrigger) to the management network or VPN. Apply egress filtering on the web tier so a compromised host cannot pull second-stage payloads via curl/wget.
      • Endpoint hardening:
        • Run the PHP worker without write access to the webroot; allow writes only to storage/ and dedicated asset volumes.
        • Use disable_functions in php.ini to disable system, exec, shell_exec, passthru and proc_open where the business allows.
      • Configuration: Isolate the PHP session directory and prevent PHP execution from upload or asset paths (nginx: location ~* /uploads/.*\.php$ { deny all; }).
      • IAM/least privilege: Limit the Craft database user to its own schema, and keep high-privilege cloud credentials out of .env.

    3. Runbook step 3

      Detection rules

      • Web access logs: Flag POSTs to generate-transform. A typical pattern is two back-to-back requests from the same IP: a token fetch, then the exploit. Example SPL: index=web method=POST (uri="*generate-transform*" OR uri_query="*generate-transform*") | stats count by src_ip, status
      • Request body/WAF logs: Alert on __class inside JSON bodies sent to Craft endpoints. Sigma shape: cs-method: POST, cs-uri|contains: 'generate-transform', request_body|contains: '__class'.
      • EDR process ancestry: Treat php-fpm, apache2 or nginx spawning sh, bash, curl, wget, base64 or python as high fidelity. Use Sysmon for Linux EID 1 or auditd execve filtered on the PHP worker's parent PID.
      • File integrity: Alert on new or modified .php files under web/ (auditd -w /var/www/<site>/web -p wa, Sysmon EID 11). Also look for PHP code inside session files under /var/lib/php/sessions.
      • Network telemetry (Zeek/Suricata): Correlate outbound connections from the web server to unfamiliar hosts, paste sites or file-sharing services shortly after POSTs to generate-transform.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: OSV (Open Source Vulnerabilities), cvelistv5, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    craftcmscms
    • ≥ 3.0.0-RC1, < 3.9.15
    • —
    craftcmscraft_cms
    • 5.0.0 – < 5.6.17
    • 3.0.0 – < 3.9.15
    • 4.0.0 – < 4.14.15
    • 5.6.17
    • 3.9.15
    • 4.14.15

    Vendors and products

    Weakness classes (CWE)

    • CWE-94Improper Control of Generation of Code ('Code Injection')

      Base

      The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

      Entry at MITRE CWE-94

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    PoC-in-GitHub (nomi-sec)CVE-2025-32432-craftcms-rce (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-32432-exploit-by-P34NUT (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-32432-PoC (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)craftcms-cve-2025-32432-rce (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-32432 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)htb-orion-writeup (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)PoC_CVE-2025-32432 (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • github.comcraftcms/cms/security/advisories/GHSA-4w8r-3xrw-v25gweb
    • github.comcraftcms/cms/security/advisories/GHSA-f3gw-9ww9-jmc3web, x_refsource_CONFIRM
    • NVD (NIST)vuln/detail/CVE-2025-32432advisory
    • github.comcraftcms/cms/commit/e1c85441fa47eeb7c688c2053f25419bc0547b47web, x_refsource_MISC
    • craftcms.comknowledge-base/craft-cms-cve-2025-32432web
    • github.comcraftcms/cmspackage
    • github.comcraftcms/cms/blob/3.x/CHANGELOG.mdweb, x_refsource_MISC
    • github.comcraftcms/cms/blob/4.x/CHANGELOG.mdweb, x_refsource_MISC
    • github.comcraftcms/cms/blob/5.x/CHANGELOG.mdweb, x_refsource_MISC
    • sensepost.comblog/2025/investigating-an-in-the-wild-campaign-using-rce-in-cr…web
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-32432web, government-resource
    • sensepost.comblog/2025/investigating-an-in-the-wild-campaign-using-rce-in-cr…Technical description, Exploit

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    One NVD translation into another language is hidden.

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-32432
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-32432"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-32432.svg?lang=en" alt="CVE-2025-32432 – NEOSEC Intel" height="20"></a>