CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2024-56145 remediation guide

Craft CMS

Craft is a flexible, user-friendly CMS for creating custom digital experiences on the web and beyond. Users of affected versions are affected by this vulnerability if their php.ini configuration has `register_argc_argv` enabled. For these users an unspecified remote code execution vector is present. Users are advised to update to version 3.9.14, 4.13.2, or 5.5.2. Users unable to upgrade should disable `register_argc_argv` to mitigate the issue.

Open CVE record
ProductCraft CMS
Affected versions>= 4.0.0-RC1, < 4.13.2, >= 5.0.0-RC1, < 5.5.2, >= 3.0.0, < 3.9.14, >= 3.0.0 < 3.9.14, >= 4.0.0 < 4.13.2, >= 5.0.0 < 5.5.2
Fixed versions3.9.14, 4.13.2, 5.5.2
Priority basisImmediate · CVSS 9.3 · EPSS 97.4%
01

Identify the affected asset

Confirm whether Craft CMS is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 4.0.0-RC1, < 4.13.2, >= 5.0.0-RC1, < 5.5.2, >= 3.0.0, < 3.9.14, >= 3.0.0 < 3.9.14, >= 4.0.0 < 4.13.2, >= 5.0.0 < 5.5.2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2024-56145 Remediation Guide | SECUFOCUS NOW