CVE-2021-21013
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 an insecure direct object vulnerability (IDOR) in the customer API module. Successful exploitation could lead to sensitive information disclosure and update arbitrary information on another user's account.
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 confidenceAn Insecure Direct Object Reference (IDOR) vulnerability in Magento 2's customer API module allows authenticated attackers to access or modify other users' account information by manipulating object references in API requests, leading to sensitive data disclosure and unauthorized account updates.
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.4.1>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 `php bin/magento --version` or check the `composer.json` file for the magento/product-community-edition or magento/product-enterprise-edition version entryAffected if The installed version is 2.3.x through 2.4.1 (including 2.4.1), as these versions contain the vulnerable customer API module code
-
Verify customer module is installed and enabledRun `php bin/magento module:status Magento_Customer` or check the `app/etc/config.php` file for `Magento_Customer` set to 1Affected if The customer module is enabled, as the IDOR flaw exists in this specific module's API implementation
-
Confirm API functionality is accessibleCheck that API endpoints are not blocked in `app/etc/env.php` under the `webapi` configuration section, and verify the customer API routes exist in `vendor/magento/module-customer/etc/webapi.xml`Affected if API access is enabled and the customer API routes are present, as the vulnerability requires sending requests to customer API endpoints
-
Check for custom API security extensionsReview any custom modules in `app/code` that modify customer API behavior, and inspect `di.xml` files for plugins intercepting customer API servicesAffected if No custom protection exists, as the vulnerability allows unauthorized access to any customer object reference without additional authorization checks in the default code
You are affected if your Magento installation runs version 2.3.x through 2.4.1 with the customer API module enabled and accessible.
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 official Magento security patch or upgrade to a patched version (2.4.2, 2.4.1-p1, or 2.3.7) to resolve the IDOR in the customer API module.
- 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-2021-21013 — 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-21013 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