Magento Commerce Insecure Direct Object Reference Could Lead To Information Disclosure

published 2021-01-13 5y ago modified 2026-06-17 4mo ago also EUVD-2021-8422

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 3.0%; EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits: 0; none known

Magento 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.

Is CVE-2021-21013 in your stack? 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

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

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	8.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD	2.0	5.5	AV:N/AC:L/Au:S/C:P/I:P/A:N

Affected products

Adobe Magento Commerce

Classification

Weakness

CWE-863 Incorrect Authorization
CWE-639 Authorization Bypass Through User-Controlled Key

References

helpx.adobe.com /security/products/magento/apsb21-08.html
release-notes, vendor-advisory

Sources

CVE List CVE-2021-21013
NVD CVE-2021-21013

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.