CVE-2020-9584
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 stored cross-site scripting vulnerability. Successful exploitation could lead to sensitive information disclosure.
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 confidenceA stored cross-site scripting (XSS) vulnerability exists in Magento versions 2.3.4 and earlier, 2.2.11 and earlier, 1.14.4.4 and earlier, and 1.9.4.4 and earlier. Attackers can inject malicious JavaScript into vulnerable input fields, which is then stored on the server and executed in the browsers of other users who view the compromised content, potentially leading to session hijacking, credential theft, and sensitive information disclosure.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 the installed Magento versionLog into the Magento admin panel and navigate to System > Configuration > Advanced > Advanced > Module_Output or use the command line: php bin/magento --version. Alternatively, check the app/etc/di.xml or composer.json file for the version number.Affected if The installed version falls within the affected ranges: Magento 1.x <= 1.9.4.4 or <= 1.14.4.4; Magento 2.2.x <= 2.2.11; Magento 2.3.x <= 2.3.4.
-
Identify vulnerable input fields that handle stored contentReview the Magento configuration for input fields that store and display user-generated content, including product descriptions, CMS blocks and pages, category descriptions, customer attributes, and review fields. These are common locations where stored XSS can be injected.Affected if Any of these input fields are accessible to untrusted users without proper input sanitization.
-
Inspect stored content in the database for malicious scriptsQuery the Magento database (typically MySQL) tables that store user-generated content, including catalog_product_entity_text, cms_block, cms_page, catalog_category_entity_text, and eav_attribute_option_value. Search for script tags, javascript: URIs, event handlers (onload, onerror, onmouseover), and encoded payloads.Affected if Any records contain suspicious JavaScript code or HTML script tags that were not intentionally added by administrators.
-
Review server access logs for XSS attack patternsExamine web server access logs (Apache, Nginx) for requests containing common XSS payloads in parameters that map to stored content fields. Look for patterns like <script, javascript:, onerror=, onload=, and various encoding techniques.Affected if Requests with XSS payloads are found targeting input fields that store content.
You are affected if your Magento version is within the vulnerable ranges AND any user-accessible input fields that store content lack proper sanitization, or if malicious scripts are already present in your database.
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 to remediate this stored XSS vulnerability. Additionally, implement Content Security Policy (CSP) headers and ensure all user inputs are properly validated and sanitized.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9584 — 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-9584 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