CVE-2021-21030
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.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are vulnerable to a stored cross-site scripting (XSS) in the customer address upload feature. Successful exploitation could lead to arbitrary JavaScript execution in the victim's browser. Exploitation of this issue requires user interaction.
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 the customer address upload feature of Magento. Attackers can inject malicious JavaScript code that persists in the database and executes when administrative users or customers view the uploaded address data in their browsers. This is a high-severity (CVSS 8.1) issue affecting multiple Magento versions.
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< 2.3.6= 2.3.6= 2.4.0= 2.4.1CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 installed Magento versionRun the CLI command 'php bin/magento --version' or check the 'composer.json' file in the Magento root directory for the 'version' fieldAffected if The installed version is 2.3.6, 2.4.0, 2.4.1, or any version prior to 2.3.6 (versions below 2.3.6)
-
Confirm customer address functionality is activeVerify the Magento installation has customer modules enabled and the address upload feature is accessible. Check the admin panel under Customers > All Customers to see if address management is availableAffected if Customer address management is enabled and accessible to either admin users or customers through storefront account creation or checkout
-
Inspect database for anomalous address entriesQuery the 'customer_address_entity' table (or equivalent address tables in your Magento database) for unexpected content in address fields such as firstname, lastname, street, city, or company. Look for entries containing script tags, javascript:, or other HTML/JavaScript patternsAffected if Address database records contain HTML script tags or JavaScript event handlers in fields where plain text is expected
-
Review admin activity logs for address-related actionsCheck admin action logs, audit trails, or security event logs for unusual bulk exports, imports, or modifications of customer address data, especially from unfamiliar IP addresses or outside normal administrative hoursAffected if Admin logs show suspicious or bulk address export/import activity that was not initiated by authorized administrators
You are affected if your Magento installation runs version 2.3.6, 2.4.0, 2.4.1, or any version below 2.3.6 AND the customer address upload feature is enabled in your 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.
From vendor data2.3.6
Apply the vendor-provided security patch or upgrade to a patched Magento version immediately. Given this is a stored XSS, review recent admin access and customer address upload logs for indicators of prior exploitation.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2021-21030 — 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-2021-21030 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