# CVE-2016-5562: Missing authorization in n/a

> Remote authenticated users can compromise confidentiality and integrity in Oracle iProcurement due to improper access controls.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-f39w-3rjp-955j

## What is CVE-2016-5562?

CVE-2016-5562 is a high-severity missing authorization vulnerability in n/a, published on 25 Oct 2016. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in the Oracle iProcurement component in Oracle E-Business Suite 12.1.1 through 12.1.3 and 12.2.3 through 12.2.6 allows remote authenticated users to affect confidentiality and integrity via unknown vectors.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Iprocurement.

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

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

## Is CVE-2016-5562 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-3151](https://insights.sbomify.com/CVE-2018-3151/): Information disclosure in iProcurement (high 7.5)
- [CVE-2023-21973](https://insights.sbomify.com/CVE-2023-21973/): Cross-site request forgery in iProcurement (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5562 is a high-severity missing authorization vulnerability in n/a, published on 25 Oct 2016. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-5562 in the wild and no public exploit code.

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

## Sources

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

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