CVE-2024-56145
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 · uneditedCraft 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.
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 confidenceCraft CMS versions prior to 3.9.14, 4.13.2, or 5.5.2 contain an unspecified remote code execution vulnerability that is only exploitable when the PHP configuration directive `register_argc_argv` is enabled. This PHP setting allows PHP scripts to access command-line arguments.
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>= 3.0.0, < 3.9.14>= 4.0.0, < 4.13.2>= 5.0.0, < 5.5.2CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Craft CMS versionLocate the version file in your Craft installation (composer.json or craft/app/etc/app.xml) or view the version in the Craft admin panel under Utilities > System ReportAffected if The installed version is 3.0.0 through 3.9.13, 4.0.0 through 4.13.1, or 5.0.0 through 5.5.1 (meaning it falls within the affected ranges)
-
Verify PHP register_argc_argv settingRun phpinfo() or inspect your php.ini file to determine the value of the register_argc_argv directiveAffected if register_argc_argv is set to On or enabled in the PHP configuration
A user is affected if their Craft CMS version is in one of the affected ranges AND PHP's register_argc_argv directive is enabled in their environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.9.144.13.25.5.2
Either upgrade Craft CMS to version 3.9.14, 4.13.2, or 5.5.2, or disable the `register_argc_argv` directive in php.ini and restart the PHP service.
Upgrade to Craft CMS 3.9.14, 4.13.2, or 5.5.2 depending on your current major version
- 1. Identify your current Craft CMS version by checking the composer.json file or the admin dashboard.
- 2. Create a complete backup of your database and files before proceeding with any upgrade.
- 3. For Craft CMS 3.x users: Update to version 3.9.14 by running composer require craftcms/cms:^3.9.14 in your project directory.
- 4. For Craft CMS 4.x users: Update to version 4.13.2 by running composer require craftcms/cms:^4.13.2 in your project directory.
- 5. For Craft CMS 5.x users: Update to version 5.5.2 by running composer require craftcms/cms:^5.5.2 in your project directory.
- 6. Run composer update to install the new version and its dependencies.
- 7. Run any pending database migrations using ./craft migrate/all as needed.
- 8. Verify the upgrade was successful by checking the version in the admin dashboard.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56145 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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