dbcve.org
CommerceApplication · Adobe

CVE-2024-20758

CRITICAL · 9.0 CVSS v3.1 Published 2024-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Adobe Commerce versions 2.4.6-p4, 2.4.5-p6, 2.4.4-p7, 2.4.7-beta3 and earlier are affected by an Improper Input Validation vulnerability that could result in arbitrary code execution on the underlying filesystem. Exploitation of this issue does not require user interaction, but the attack complexity is high.

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

Adobe Commerce versions 2.4.6-p4, 2.4.5-p6, 2.4.4-p7, 2.4.7-beta3 and earlier contain an improper input validation vulnerability that allows attackers to execute arbitrary code on the underlying filesystem. The vulnerability is exploitable without user interaction but requires high attack complexity.

MitigationApply the vendor-supplied security patches (2.4.6-p5, 2.4.5-p7, 2.4.4-p8 or later) or upgrade to the latest stable Adobe Commerce version. Until patched, review and restrict input handling in exposed endpoints.

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
CommerceApplication
Affected:all versions= 2.3.7= 2.4.0= 2.4.1= 2.4.2= 2.4.3= 2.4.4= 2.4.5= 2.4.6= 2.4.7
MagentoCMS
Affected:= 2.4.4= 2.4.5= 2.4.6= 2.4.7

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify if Adobe Commerce or Magento is installed
    Look for composer.json in the web root, or check for the typical Magento directory structure (app/code/Magento, var/generation, pub/index.php). Alternatively, check the admin panel footer for the version number.
    Affected if Adobe Commerce or Magento software is found on the system
  2. Determine the installed version
    Run 'composer show magento/product-enterprise-edition 2>/dev/null | grep version' or 'composer show magento/community-edition 2>/dev/null | grep version' from the project root. Or check the version in composer.lock file under the magento package entry.
    Affected if The version shown is 2.3.7, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, or 2.4.7, or any version earlier than 2.4.4-p8, 2.4.5-p7, or 2.4.6-p5
  3. Check if patches have been applied
    Inspect the app/etc/config.php file for the patch version references, or check the composer.json for the applied patch version in the 'replace' or extra sections. Also check the composer.lock for patched version entries.
    Affected if No security patches (2.4.6-p5, 2.4.5-p7, or 2.4.4-p8) are reflected in the installation and the base version remains in the affected range
  4. Determine network exposure of admin or exposed endpoints
    Review web server configuration and firewall rules to identify if the Magento admin panel (/admin) or any custom endpoints handling file operations are accessible from untrusted networks.
    Affected if The admin panel or endpoints processing user-supplied input are reachable from the internet or untrusted networks, increasing the attack surface

The environment is affected if Adobe Commerce or Magento is installed with a version between 2.3.7 and 2.4.7 (including all patch levels before p8/p7/p5) and the vulnerable input handling code is accessible without additional authentication barriers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied security patches (2.4.6-p5, 2.4.5-p7, 2.4.4-p8 or later) or upgrade to the latest stable Adobe Commerce version. Until patched, review and restrict input handling in exposed endpoints.

Recommended fix High confidence

Adobe Commerce 2.4.7 (stable) or latest patch (2.4.6-p5+, 2.4.5-p7+, 2.4.4-p8+)

  1. 1. Backup your Adobe Commerce/Magento database and filesystem
  2. 2. Review the Adobe Commerce release notes at helpx.adobe.com for version 2.4.7 and associated security patches
  3. 3. Upgrade to Adobe Commerce 2.4.7 (stable release) or apply the latest security patch for your current version line (e.g., 2.4.6-p5, 2.4.5-p7, or 2.4.4-p8)
  4. 4. After upgrade, clear the cache: bin/magento cache:flush
  5. 5. Verify the upgrade by checking the admin panel and running bin/magento --version
  6. 6. Test critical commerce workflows (checkout, catalog, customer accounts) to ensure functionality
Caveat Major upgrades to 2.4.7 may require PHP version updates (PHP 8.1+ required) and compatibility checks for third-party extensions; review extension compatibility before upgrading

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

Fix this in Commerce Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20758 — 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-2024-20758 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