# CVE-2019-2771: Missing authorization in BI Publisher (formerly XML Publisher)

> Low-privileged attackers can modify, read, or disrupt BI Publisher data via HTTP with user interaction, requiring immediate patching.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:L`)
- **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:** 23 Jul 2019
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-rpmx-h4jc-7v2q

## What is CVE-2019-2771?

CVE-2019-2771 is a high-severity missing authorization vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 23 Jul 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### 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 and 12.2.1.3.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise BI Publisher (formerly XML Publisher). Successful attacks require human interaction from a person other than the attacker and 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 creation, deletion or modification access to critical data or all BI Publisher (formerly XML Publisher) accessible data as well as unauthorized read access to a subset of BI Publisher (formerly XML Publisher) accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of BI Publisher (formerly XML Publisher). CVSS 3.0 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:L).

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

It affects 1 product.


Products: Oracle Bi Publisher.

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

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

## Is CVE-2019-2771 being exploited?

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

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

- [CVE-2026-71059](https://insights.sbomify.com/CVE-2026-71059/): Auth bypass in Oracle BI Publisher (critical 9.9)
- [CVE-2026-60719](https://insights.sbomify.com/CVE-2026-60719/): Privilege escalation in Oracle BI Publisher (critical 9.9)
- [CVE-2026-60173](https://insights.sbomify.com/CVE-2026-60173/): Auth bypass in Oracle BI Publisher (critical 9.8)
- [CVE-2024-21082](https://insights.sbomify.com/CVE-2024-21082/): XML external entity in BI Publisher (formerly XML Publisher) (critical 9.8)
- [CVE-2026-71058](https://insights.sbomify.com/CVE-2026-71058/): Auth bypass in Oracle BI Publisher (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2771 is a high-severity missing authorization vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 23 Jul 2019. 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-2019-2771 in the wild and no public exploit code.

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-2771/ (Markdown: https://insights.sbomify.com/CVE-2019-2771/index.md)
```

## Sources

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

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