# CVE-2021-21012: Magento Commerce Insecure Direct Object Reference Vulnerability Could Lead To Sensitive Information Disclosure

> Attackers can exploit an insecure direct object reference in the checkout module to access sensitive information.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6vpq-pcm8-6pgw

## What is CVE-2021-21012?

CVE-2021-21012 is a medium-severity vulnerability in Adobe Magento Commerce, published on 13 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 checkout module. Successful exploitation could lead to sensitive information disclosure.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2021-21012?

It affects 2 products.


Products: Adobe Magento Commerce, Adobe Magento Open Source.

## How do I fix CVE-2021-21012?

No fix has been published for CVE-2021-21012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-21012 being exploited?

There is no known exploitation of CVE-2021-21012 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-21012 and fix it if it is affected.

What it is: CVE-2021-21012 is a medium-severity vulnerability in Adobe Magento Commerce, published on 13 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-21012 in the wild and no public exploit code.

Affected product: Adobe Magento Commerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-21012/ (Markdown: https://insights.sbomify.com/CVE-2021-21012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-21012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-21012
- OSV: https://osv.dev/vulnerability/CVE-2021-21012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-21012/
Summaries are generated and may contain mistakes; the official description above is the record.