# CVE-2019-2616: Oracle BI Publisher Unauthorized Access

> Unauthenticated attackers can modify and read BI Publisher data via HTTP, requiring immediate patching for Oracle Fusion Middleware users.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2019
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-8j2r-c64f-x52g

## What is CVE-2019-2616?

CVE-2019-2616 is a high-severity missing authorization vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the BI Publisher (formerly XML Publisher) component of Oracle Fusion Middleware (subcomponent: BI Publisher Security). Supported versions that are affected are 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher). While the vulnerability is in BI Publisher (formerly XML Publisher), attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of BI Publisher (formerly XML Publisher) accessible data as well as unauthorized read access to a subset of BI Publisher (formerly XML Publisher) accessible data. CVSS 3.0 Base Score 7.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2019-2616?

It affects 1 product.


Products: Oracle Business Intelligence Publisher.

## How do I fix CVE-2019-2616?

No fix has been published for CVE-2019-2616 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2019-2616 being exploited?

Yes. Attackers have exploited CVE-2019-2616 in the wild since at least 25 Mar 2022.

Public exploit code:

- Oracle Business Intelligence / XML Publisher 11.1.1.9.0 / 12.2.1.3.0 / 12.2.1.4.0 - XML External Entity Injection (exploitdb)
- Oracle Business Intelligence/XML Publisher - XML External Entity Injection (nuclei): http/cves/2019/CVE-2019-2616.yaml

## Other vulnerabilities in Oracle Corporation BI Publisher (formerly XML Publisher)

- [CVE-2020-14879](https://insights.sbomify.com/CVE-2020-14879/): Information disclosure in BI Publisher (formerly XML Publisher) (high 8.5)
- [CVE-2020-14880](https://insights.sbomify.com/CVE-2020-14880/): Information disclosure in BI Publisher (formerly XML Publisher) (high 8.5)
- [CVE-2020-14784](https://insights.sbomify.com/CVE-2020-14784/): Cross-site scripting in BI Publisher (formerly XML Publisher) (high 8.2)
- [CVE-2020-14842](https://insights.sbomify.com/CVE-2020-14842/): Information disclosure in BI Publisher (formerly XML Publisher) (high 8.2)
- [CVE-2019-2906](https://insights.sbomify.com/CVE-2019-2906/): Cross-site scripting in BI Publisher (formerly XML Publisher) (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2616 and fix it if it is affected.

What it is: CVE-2019-2616 is a high-severity missing authorization vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-2616 in the wild since at least 25 Mar 2022.

Affected product: Oracle Corporation BI Publisher (formerly XML Publisher). 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-2019-2616/ (Markdown: https://insights.sbomify.com/CVE-2019-2616/index.md)
```

## Sources

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

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