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

> Remote attackers can access confidential information in Oracle E-Business Suite via Workflow Events in the Shipping Execution component.

- **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:** 25 Oct 2016
- **Updated:** 10 Oct 2024
- **Also known as:** GHSA-rqc5-6hwx-2mpg

## What is CVE-2016-5532?

CVE-2016-5532 is a medium-severity vulnerability in n/a, published on 25 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle Shipping Execution component in Oracle E-Business Suite 12.1.1 through 12.1.3 and 12.2.3 through 12.2.6 allows remote attackers to affect confidentiality via vectors related to Workflow Events.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Oracle Shipping Execution.

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

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

## Is CVE-2016-5532 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-35563](https://insights.sbomify.com/CVE-2021-35563/): Missing authorization in Shipping Execution (high 8.1)
- [CVE-2026-60918](https://insights.sbomify.com/CVE-2026-60918/): Privilege escalation in Oracle Shipping Execution (high 7.2)
- [CVE-2026-62475](https://insights.sbomify.com/CVE-2026-62475/): Auth bypass in Oracle Shipping Execution (medium 6.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5532 is a medium-severity vulnerability in n/a, published on 25 Oct 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-5532 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-5532/ (Markdown: https://insights.sbomify.com/CVE-2016-5532/index.md)
```

## Sources

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

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