Skip to content
Fencer Intel
medium 5.3

CVE-2021-21020 json

Magento Commerce Improper Access Control Vulnerability

published 5y ago modified 2mo ago also BIT-magento-2021-21020 , EUVD-2022-2001 , GHSA-2j6v-829g-885q

cvss
5.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

Magento versions 2.4.1 (and earlier), 2.4.0-p1 (and earlier) and 2.3.6 (and earlier) are vulnerable to an access control bypass vulnerability in the Login as Customer module. Successful exploitation could lead to unauthorized access to restricted resources.

Patch / fix

  • packagist magento/community-edition 2.3.6, 2.4.1-p1
  • bitnami magento 2.3.6, 2.4.1
  • magento magento 2.3.6

Is CVE-2021-21020 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N
OSV 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
packagist magento/community-edition
<2.3.6
>=2.4.0, <2.4.1-p1
2.3.6
2.4.1-p1
packagist magento/project-community-edition
<=2.0.2
 no fix listed
bitnami magento
<2.3.6
>=2.4.0, <2.4.1
2.3.6
2.4.1

Affected products

  • Adobe Magento Commerce

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.