# CVE-2018-2791: Cross-site scripting in WebCenter Sites

> Unauthenticated attackers can exploit a cross-site scripting flaw in Oracle WebCenter Sites to access sensitive data and modify content via HTTP.

- **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 Apr 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-p8p6-rvh2-gwj9

## What is CVE-2018-2791?

CVE-2018-2791 is a high-severity cross-site scripting vulnerability in Oracle Webcenter Sites, published on 19 Apr 2018. 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 Sites component of Oracle Fusion Middleware (subcomponent: Advanced UI). Supported versions that are affected are 11.1.1.8.0, 12.2.1.2.0 and 12.2.1.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebCenter Sites. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle WebCenter Sites, 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 Sites accessible data as well as unauthorized update, insert or delete access to some of Oracle WebCenter Sites 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-2018-2791?

It affects 1 product.


Products: Oracle Webcenter Sites.

## How do I fix CVE-2018-2791?

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

## Is CVE-2018-2791 being exploited?

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

Public exploit code:

- Oracle WebCenter Sites 11.1.1.8.0/12.2.1.x - Cross-Site Scripting (exploitdb)
- Oracle Fusion Middleware WebCenter Sites - Cross-Site Scripting (nuclei): http/cves/2018/CVE-2018-2791.yaml

## Other vulnerabilities in Oracle Webcenter Sites

- [CVE-2026-46798](https://insights.sbomify.com/CVE-2026-46798/): Auth bypass in Oracle WebCenter Sites (critical 10.0)
- [CVE-2026-46800](https://insights.sbomify.com/CVE-2026-46800/): Auth bypass in Oracle WebCenter Sites (critical 10.0)
- [CVE-2026-61021](https://insights.sbomify.com/CVE-2026-61021/): Auth bypass in Oracle WebCenter Sites (critical 9.9)
- [CVE-2026-60552](https://insights.sbomify.com/CVE-2026-60552/): Auth bypass in Oracle WebCenter Sites (critical 9.9)
- [CVE-2026-61018](https://insights.sbomify.com/CVE-2026-61018/): Auth bypass in Oracle WebCenter Sites (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2791 and fix it if it is affected.

What it is: CVE-2018-2791 is a high-severity cross-site scripting vulnerability in Oracle Webcenter Sites, published on 19 Apr 2018. 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-2018-2791 exists.

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

## Sources

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

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