# CVE-2017-10060: Cross-site scripting in Business Intelligence Enterprise Edition

> Unauthenticated attackers can exploit cross-site scripting to access critical data and modify some data in Oracle Business Intelligence Enterprise Edition.

- **Severity:** High 8.2 (`CVSS:3.0/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:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-x2ff-4qvr-4vpj

## What is CVE-2017-10060?

CVE-2017-10060 is a high-severity cross-site scripting vulnerability in Oracle Business Intelligence, published on 19 Oct 2017. 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 Oracle Business Intelligence Enterprise Edition component of Oracle Fusion Middleware (subcomponent: Analytics Web General). Supported versions that are affected are 11.1.1.7.0, 11.1.1.9.0, 12.2.1.1.0 and 12.2.1.2.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Business Intelligence Enterprise Edition, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Business Intelligence Enterprise Edition accessible data as well as unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition 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-2017-10060?

It affects 1 product.


Products: Oracle Business Intelligence.

## How do I fix CVE-2017-10060?

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

## Is CVE-2017-10060 being exploited?

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

## Other vulnerabilities in Oracle Business Intelligence

- [CVE-2020-14864](https://insights.sbomify.com/CVE-2020-14864/): Oracle Business Intelligence Enterprise Edition Path Transversal (high 7.5, exploited in the wild)
- [CVE-2021-2456](https://insights.sbomify.com/CVE-2021-2456/): Auth bypass in Business Intelligence Enterprise Edition (critical 9.8)
- [CVE-2020-2950](https://insights.sbomify.com/CVE-2020-2950/): Auth bypass in Oracle Business Intelligence Enterprise Edition (critical 9.8)
- [CVE-2026-71055](https://insights.sbomify.com/CVE-2026-71055/): Auth bypass in Oracle Business Intelligence Enterprise Edition (high 8.8)
- [CVE-2026-60671](https://insights.sbomify.com/CVE-2026-60671/): Missing authorization in Oracle Business Intelligence Enterprise Edition (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10060 and fix it if it is affected.

What it is: CVE-2017-10060 is a high-severity cross-site scripting vulnerability in Oracle Business Intelligence, published on 19 Oct 2017. 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-2017-10060 in the wild and no public exploit code.

Affected product: Oracle Business Intelligence. 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-2017-10060/ (Markdown: https://insights.sbomify.com/CVE-2017-10060/index.md)
```

## Sources

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

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