# CVE-2020-2597: Cross-site scripting in One-to-One Fulfillment

> Unauthenticated attackers can exploit a cross-site scripting flaw in Oracle One-to-One Fulfillment to modify accessible data via network access.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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:** 15 Jan 2020
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-3265-mvvq-h76g

## What is CVE-2020-2597?

CVE-2020-2597 is a medium-severity cross-site scripting vulnerability in Oracle Corporation One-to-One Fulfillment, published on 15 Jan 2020. 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 One-to-One Fulfillment product of Oracle E-Business Suite (component: Call Phone Number Page). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle One-to-One Fulfillment. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle One-to-One Fulfillment, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle One-to-One Fulfillment accessible data. CVSS 3.0 Base Score 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N).

## Which versions are affected by CVE-2020-2597?

It affects 1 product.


Products: Oracle One-to-One Fulfillment.

## How do I fix CVE-2020-2597?

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

## Is CVE-2020-2597 being exploited?

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

## Other vulnerabilities in Oracle Corporation One-to-One Fulfillment

- [CVE-2021-2100](https://insights.sbomify.com/CVE-2021-2100/): Missing authorization in One-to-One Fulfillment (critical 9.1)
- [CVE-2021-2101](https://insights.sbomify.com/CVE-2021-2101/): Missing authorization in One-to-One Fulfillment (critical 9.1)
- [CVE-2016-8325](https://insights.sbomify.com/CVE-2016-8325/): Missing authorization in One-to-One Fulfillment (critical 9.1)
- [CVE-2021-2094](https://insights.sbomify.com/CVE-2021-2094/): Information disclosure in One-to-One Fulfillment (high 8.2)
- [CVE-2020-14819](https://insights.sbomify.com/CVE-2020-14819/): Information disclosure in One-to-One Fulfillment (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-2597 and fix it if it is affected.

What it is: CVE-2020-2597 is a medium-severity cross-site scripting vulnerability in Oracle Corporation One-to-One Fulfillment, published on 15 Jan 2020. 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-2020-2597 in the wild and no public exploit code.

Affected product: Oracle Corporation One-to-One Fulfillment. 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-2020-2597/ (Markdown: https://insights.sbomify.com/CVE-2020-2597/index.md)
```

## Sources

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

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