# CVE-2018-2609: Cross-site scripting in Agile PLM Framework

> Unauthenticated attackers can exploit a cross-site scripting vulnerability in Oracle Agile PLM to read and modify accessible data via HTTP.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 18 Jan 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-j7j7-mp2w-xjr4

## What is CVE-2018-2609?

CVE-2018-2609 is a medium-severity cross-site scripting vulnerability in Oracle Agile Product Lifecycle Management, published on 18 Jan 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 Agile PLM component of Oracle Supply Chain Products Suite (subcomponent: Security). Supported versions that are affected are 9.3.5 and 9.3.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Agile PLM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Agile PLM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Agile PLM accessible data as well as unauthorized read access to a subset of Oracle Agile PLM accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2018-2609?

It affects 1 product.


Products: Oracle Agile Product Lifecycle Management.

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

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

## Is CVE-2018-2609 being exploited?

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

## Other vulnerabilities in Oracle Agile Product Lifecycle Management

- [CVE-2024-20953](https://insights.sbomify.com/CVE-2024-20953/): Oracle Agile Product Lifecycle Management (PLM) Deserialization (high 8.8, exploited in the wild)
- [CVE-2024-21287](https://insights.sbomify.com/CVE-2024-21287/): Oracle Agile Product Lifecycle Management (PLM) Incorrect Authorization (high 7.5, exploited in the wild)
- [CVE-2019-2725](https://insights.sbomify.com/CVE-2019-2725/): Oracle WebLogic Server, Injection (high 7.5, exploited in the wild)
- [CVE-2025-21556](https://insights.sbomify.com/CVE-2025-21556/): Missing authorization in Oracle Agile PLM Framework (critical 9.9)
- [CVE-2026-71040](https://insights.sbomify.com/CVE-2026-71040/): Auth bypass in Oracle Agile PLM (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2609 is a medium-severity cross-site scripting vulnerability in Oracle Agile Product Lifecycle Management, published on 18 Jan 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: There is no known exploitation of CVE-2018-2609 in the wild and no public exploit code.

Affected product: Oracle Agile Product Lifecycle Management. 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-2609/ (Markdown: https://insights.sbomify.com/CVE-2018-2609/index.md)
```

## Sources

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

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