dbcve.org
MagentoCMS

CVE-2020-24407

CRITICAL · 9.1 CVSS v3.1 Published 2020-11-09
Fix available
A fix is available. Upgrade to 2.3.5 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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
Magento versions 2.4.0 and 2.3.5p1 (and earlier) are affected by an unsafe file upload vulnerability that could result in arbitrary code execution. This vulnerability could be abused by authenticated users with administrative permissions to the System/Data and Transfer/Import components.

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

Magento versions 2.4.0 and 2.3.5p1 and earlier contain an unsafe file upload vulnerability in the System/Data and Transfer/Import admin components. Authenticated users with administrative permissions can upload malicious files that result in arbitrary code execution on the server.

MitigationUpgrade to the patched Magento version immediately. Until then, restrict administrative access to only necessary personnel and consider disabling or monitoring the Import functionality.

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
MagentoCMS
Affected:< 2.3.5= 2.3.5= 2.4.0

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

CVSS:3.1/AV:N/AC:L/PR:H/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 Magento installation
    Look for Magento-specific files or directories such as composer.json, app/etc/di.xml, pub/index.php, or the magento directory structure in the web root.
    Affected if The application is not Magento (this CVE does not apply).
  2. Determine installed Magento version
    Check the composer.json file in the root directory for the 'version' field, or run 'php bin/magento --version' from the command line if available.
    Affected if The installed version is 2.4.0, 2.3.5, or any version lower than 2.3.5.
  3. Verify admin access is possible
    Attempt to access the admin panel URL (typically /admin or /backend) and confirm that administrative authentication is configured and reachable.
    Affected if The admin panel is exposed and reachable without additional network restrictions.
  4. Confirm Import functionality is enabled
    Log into the admin panel and navigate to System > Data Transfer > Import, or check if the import functionality has not been disabled in the configuration.
    Affected if The Import feature under System > Data Transfer is accessible and enabled.

A user is affected if they are running Magento version 2.4.0, 2.3.5, or any version below 2.3.5, and the admin panel with Import functionality is accessible.

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 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Upgrade to the patched Magento version immediately. Until then, restrict administrative access to only necessary personnel and consider disabling or monitoring the Import functionality.

Recommended fix High confidence

Magento 2.3.6 or Magento 2.4.1 (or latest available 2.3.x/2.4.x releases)

  1. 1. Verify current Magento installation version using bin/magento --version or admin panel
  2. 2. Create a full backup of the Magento database and files
  3. 3. Put Magento in maintenance mode: bin/magento maintenance:enable
  4. 4. Upgrade Magento via composer: composer require magento/product-community-edition:<fixed_version> --no-update
  5. 5. Update dependencies: composer update
  6. 6. Clear cache and regenerate static content: bin/magento cache:flush && bin/magento setup:static-content:deploy
  7. 7. Run database upgrades: bin/magento setup:upgrade
  8. 8. Reindex: bin/magento indexer:reindex
Caveat Standard upgrade risks apply - test thoroughly in staging environment before production deployment, especially custom theme and extension compatibility

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

Fix this in Magento Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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