# CVE-2017-10075: Information disclosure in WebCenter Content

> Unauthenticated attackers can access critical data and modify some content in Oracle WebCenter Content via HTTP, requiring user interaction.

- **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:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-qrgx-3g5f-wv73

## What is CVE-2017-10075?

CVE-2017-10075 is a high-severity vulnerability in Oracle Webcenter Content, published on 8 Aug 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 WebCenter Content component of Oracle Fusion Middleware (subcomponent: Content Server). Supported versions that are affected are 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 WebCenter Content. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle WebCenter Content, 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 WebCenter Content accessible data as well as unauthorized update, insert or delete access to some of Oracle WebCenter Content 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-10075?

It affects 1 product.


Products: Oracle Webcenter Content.

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

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

## Is CVE-2017-10075 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-10075 exists.

Public exploit code:

- Oracle Content Server - Cross-Site Scripting (nuclei): http/cves/2017/CVE-2017-10075.yaml

## Other vulnerabilities in Oracle Webcenter Content

- [CVE-2026-60644](https://insights.sbomify.com/CVE-2026-60644/): Auth bypass in Oracle WebCenter Content (critical 10.0)
- [CVE-2026-60663](https://insights.sbomify.com/CVE-2026-60663/): Privilege escalation in Oracle WebCenter Content (critical 9.9)
- [CVE-2026-35316](https://insights.sbomify.com/CVE-2026-35316/): Auth bypass in Oracle WebCenter Content (critical 9.9)
- [CVE-2026-35321](https://insights.sbomify.com/CVE-2026-35321/): Auth bypass in Oracle WebCenter Content (critical 9.9)
- [CVE-2026-35323](https://insights.sbomify.com/CVE-2026-35323/): Auth bypass in Oracle WebCenter Content (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10075 is a high-severity vulnerability in Oracle Webcenter Content, published on 8 Aug 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-10075 exists.

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

## Sources

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

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