CVE-2020-9585
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 · uneditedMagento versions 2.3.4 and earlier, 2.2.11 and earlier (see note), 1.14.4.4 and earlier, and 1.9.4.4 and earlier have a defense-in-depth security mitigation vulnerability. Successful exploitation could lead to arbitrary code execution.
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 · moderate confidenceThis is a defense-in-depth security mitigation vulnerability in Magento e-commerce platforms. Successful exploitation could lead to arbitrary code execution, indicating the vulnerability allows bypassing security controls to execute malicious code on the affected system.
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<= 1.9.4.4<= 1.14.4.4>= 2.2.0, <= 2.2.11>= 2.3.0, <= 2.3.4CVSS 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.
-
Identify Magento installation typeLocate the Magento installation directory. Check for app/etc/config.php or composer.json in the web root. Magento 1 typically has mage script or downloader, while Magento 2 has bin/magento CLI.Affected if This is a preliminary step to determine which Magento version detection method to use.
-
Determine installed Magento versionFor Magento 2: Run 'php bin/magento --version' from the installation directory, or check the 'version' field in composer.json. For Magento 1: Check app/Mage.php for the version constant, or view the admin panel footer which displays the version number.Affected if This step obtains the exact version number needed for comparison.
-
Compare version against affected rangesCheck if the installed version falls within any of these ranges: Magento 1.9.x <= 1.9.4.4, Magento 1.14.x <= 1.14.4.4, Magento 2.2.x >= 2.2.0 and <= 2.2.11, or Magento 2.3.x >= 2.3.0 and <= 2.3.4.Affected if The installed version matches any of the affected version ranges indicates the environment is vulnerable.
-
Verify patch application statusFor Magento 2: Check if security patch SUPEE-10888 or MDVA-XXXXX (check Magento release notes for the specific patch ID for CVE-2020-9585) has been applied by reviewing applied patches in composer.json or checking magento_patches list via CLI. For Magento 1: Check app/etc/applied.patches.list for the relevant security patch.Affected if The specific CVE-2020-9585 security patch is absent from the applied patches list, indicating the vulnerability remains unmitigated.
The environment is affected if the installed Magento version falls within the affected ranges AND the corresponding security patch has not been applied.
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.
From vendor dataApply the available Magento security patches or upgrade to a supported version beyond 2.3.4/2.2.11 for Magento 2 or beyond 1.14.4.4/1.9.4.4 for Magento 1. Given the critical severity (CVSS 9.8), this should be prioritized immediately.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9585 — 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-2020-9585 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