CVE-2021-28567
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.2 (and earlier), 2.4.1-p1 (and earlier) and 2.3.6-p1 (and earlier) are vulnerable to an Improper Authorization vulnerability in the customers module. Successful exploitation could allow a low-privileged user to modify customer data. Access to the admin console is required for successful exploitation.
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 confidenceMagento versions 2.4.2 and earlier contain an Improper Authorization vulnerability in the customers module. A low-privileged admin user can modify customer data beyond their authorized scope. The attack requires admin console access, making this an authorization bypass within the administrative interface.
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.2CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Determine installed Magento versionLog into the admin panel and navigate to System > Settings > About or run the CLI command: php bin/magento --versionAffected if The version is 2.4.2 or earlier (any version up to and including 2.4.2)
-
Identify admin users with limited privilegesNavigate to System > Permissions > All Users in the admin panel. Review the roles assigned to each admin user, particularly looking for users with limited or custom roles rather than full administrator access.Affected if There exist admin users with limited/custom roles accessing the admin panel (low-privilege users who could exploit the authorization bypass)
-
Verify customer module role permissionsNavigate to System > Permissions > User Roles. For each limited role, click to edit and expand the Customers section. Verify whether the role has permissions to modify customer information beyond what that user should legitimately access.Affected if Limited-role admin users have customer write/modify permissions that exceed what they should be granted based on their job function
-
Check for unauthorized customer data modificationsReview admin action logs or customer modification histories (System > Action Log > Report if available) to identify if low-privilege admin users have been modifying customer records outside their expected scope.Affected if Logs show low-privilege admin users modifying customer data they should not have access to modify
Your environment is affected if you run Magento version 2.4.2 or earlier AND have admin users with limited privileges accessing the customers module, as the vulnerability allows those low-privileged users to modify customer data beyond their authorized scope.
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.
dbcve · scopedApply the official Magento security patch for CVE-2021-28567 or upgrade to a patched Magento version. After patching, verify that role-based access controls properly restrict customer data modifications based on user privileges.
Magento 2.4.3 (or latest 2.4.x stable release)
- 1. Backup your current Magento 2.4.2 (or earlier) installation including database and files
- 2. Review the upgrade path: Magento 2.4.2 -> 2.4.3 (or latest 2.4.x)
- 3. Update composer.json to require the target version: composer require magento/product-community-edition=2.4.3 --no-update
- 4. Run composer update to fetch new packages: composer update
- 5. Clear the cache and generated files: rm -rf var/cache var/generation generated/code
- 6. Run the upgrade script: php bin/magento setup:upgrade
- 7. Re-compile dependency injection: php bin/magento setup:di:compile
- 8. Deploy static content: php bin/magento setup:static-content:deploy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28567 — 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-28567 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