# CVE-2018-2898: Cross-site scripting in FLEXCUBE Investor Servicing

> Unauthenticated attackers can exploit a cross-site scripting vulnerability in Oracle FLEXCUBE Investor Servicing to read and modify 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 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-c22r-jqv5-964q

## What is CVE-2018-2898?

CVE-2018-2898 is a medium-severity cross-site scripting vulnerability in Oracle Corporation FLEXCUBE Investor Servicing, published on 18 Jul 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 FLEXCUBE Investor Servicing component of Oracle Financial Services Applications (subcomponent: Infrastructure). Supported versions that are affected are 12.0.4, 12.1.0, 12.3.0 and 12.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle FLEXCUBE Investor Servicing. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle FLEXCUBE Investor Servicing, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle FLEXCUBE Investor Servicing accessible data as well as unauthorized read access to a subset of Oracle FLEXCUBE Investor Servicing 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-2898?

It affects 1 product.


Products: Oracle Flexcube Investor Servicing.

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

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

## Is CVE-2018-2898 being exploited?

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

## Other vulnerabilities in Oracle Corporation FLEXCUBE Investor Servicing

- [CVE-2026-21973](https://insights.sbomify.com/CVE-2026-21973/): Missing authorization in Oracle FLEXCUBE Investor Servicing (high 8.1)
- [CVE-2020-14569](https://insights.sbomify.com/CVE-2020-14569/): Missing authorization in FLEXCUBE Investor Servicing (high 8.1)
- [CVE-2019-2841](https://insights.sbomify.com/CVE-2019-2841/): Missing authorization in FLEXCUBE Investor Servicing (high 8.1)
- [CVE-2018-3035](https://insights.sbomify.com/CVE-2018-3035/): Missing authorization in FLEXCUBE Investor Servicing (high 8.1)
- [CVE-2016-8315](https://insights.sbomify.com/CVE-2016-8315/): Missing authorization in FLEXCUBE Investor Servicing (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2898 is a medium-severity cross-site scripting vulnerability in Oracle Corporation FLEXCUBE Investor Servicing, published on 18 Jul 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-2898 in the wild and no public exploit code.

Affected product: Oracle Corporation FLEXCUBE Investor Servicing. 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-2898/ (Markdown: https://insights.sbomify.com/CVE-2018-2898/index.md)
```

## Sources

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

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