# CVE-2016-2212: Information disclosure in n/a

> Remote attackers can obtain sensitive order information by manipulating the order_id in RSS feed requests, exposing customer data.

- **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:** 15 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w8v6-3q9c-7754

## What is CVE-2016-2212?

CVE-2016-2212 is a medium-severity vulnerability in Magento Magento, published on 15 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The getOrderByStatusUrlKey function in the Mage_Rss_Helper_Order class in app/code/core/Mage/Rss/Helper/Order.php in Magento Enterprise Edition before 1.14.2.3 and Magento Community Edition before 1.9.2.3 allows remote attackers to obtain sensitive order information via the order_id in a JSON object in the data parameter in an RSS feed request to index.php/rss/order/status.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-2212?

It affects 1 product.


Products: Magento Magento.

## How do I fix CVE-2016-2212?

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

## Is CVE-2016-2212 being exploited?

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

## Other vulnerabilities in Magento Magento

- [CVE-2020-9664](https://insights.sbomify.com/CVE-2020-9664/): Magento php object injection vulnerability (critical 9.8)
- [CVE-2020-9576](https://insights.sbomify.com/CVE-2020-9576/): Magento command injection vulnerability (critical 9.8)
- [CVE-2020-9578](https://insights.sbomify.com/CVE-2020-9578/): Magento command injection vulnerability (critical 9.8)
- [CVE-2020-9579](https://insights.sbomify.com/CVE-2020-9579/): Magento Security mitigation bypass vulnerability (critical 9.8)
- [CVE-2020-9580](https://insights.sbomify.com/CVE-2020-9580/): Magento Security mitigation bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2212 and fix it if it is affected.

What it is: CVE-2016-2212 is a medium-severity vulnerability in Magento Magento, published on 15 Apr 2016. 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-2016-2212 in the wild and no public exploit code.

Affected product: Magento Magento. 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-2016-2212/ (Markdown: https://insights.sbomify.com/CVE-2016-2212/index.md)
```

## Sources

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

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