# CVE-2019-2906: Cross-site scripting in BI Publisher (formerly XML Publisher)

> An unauthenticated attacker can exploit a cross-site scripting vulnerability in Oracle BI Publisher to access sensitive data and modify records via HTTP.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2019
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-86xc-qfwv-3g73

## What is CVE-2019-2906?

CVE-2019-2906 is a high-severity cross-site scripting vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the BI Publisher (formerly XML Publisher) product of Oracle Fusion Middleware (component: Mobile Service). 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). 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 access to critical data or complete access to all BI Publisher (formerly XML Publisher) accessible data as well as unauthorized update, insert or delete access to some of BI Publisher (formerly XML Publisher) accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).

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

It affects 1 product.


Products: Oracle Business Intelligence Publisher.

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

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

## Is CVE-2019-2906 being exploited?

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

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

- [CVE-2019-2616](https://insights.sbomify.com/CVE-2019-2616/): Oracle BI Publisher Unauthorized Access (high 7.2, exploited in the wild)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2906 is a high-severity cross-site scripting vulnerability in Oracle Corporation BI Publisher (formerly XML Publisher), published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-2906 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-2906/ (Markdown: https://insights.sbomify.com/CVE-2019-2906/index.md)
```

## Sources

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

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