# CVE-2018-2661: Other in Financial Services Analytical Applications Infrastructure

> Unauthenticated attackers can modify and read data in Oracle Financial Services Analytical Applications Infrastructure via HTTP with user interaction.

- **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-qww4-ppcx-xwfp

## What is CVE-2018-2661?

CVE-2018-2661 is a medium-severity vulnerability in Oracle Financial Services Analytical Applications Infrastructure, 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 Financial Services Analytical Applications Infrastructure component of Oracle Financial Services Applications (subcomponent: Core). Supported versions that are affected are 7.3.5.x and 8.0.x. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Financial Services Analytical Applications Infrastructure. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Financial Services Analytical Applications Infrastructure, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Financial Services Analytical Applications Infrastructure accessible data as well as unauthorized read access to a subset of Oracle Financial Services Analytical Applications Infrastructure 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-2661?

It affects 1 product.


Products: Oracle Financial Services Analytical Applications Infrastructure.

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

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

## Is CVE-2018-2661 being exploited?

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

## Other vulnerabilities in Oracle Financial Services Analytical Applications Infrastructure

- [CVE-2025-53037](https://insights.sbomify.com/CVE-2025-53037/): Auth bypass in Oracle Financial Services Analytical Applications Infrastructure (critical 9.8)
- [CVE-2025-53036](https://insights.sbomify.com/CVE-2025-53036/): Information disclosure in Oracle Financial Services Analytical Applications Infrastructure (high 8.6)
- [CVE-2020-14824](https://insights.sbomify.com/CVE-2020-14824/): Denial of service in Financial Services Analytical Applications Infrastructure (high 8.6)
- [CVE-2025-61751](https://insights.sbomify.com/CVE-2025-61751/): Missing authorization in Oracle Financial Services Analytical Applications Infrastructure (high 8.1)
- [CVE-2026-22010](https://insights.sbomify.com/CVE-2026-22010/): Auth bypass in Oracle Financial Services Analytical Applications Infrastructure (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2661 is a medium-severity vulnerability in Oracle Financial Services Analytical Applications Infrastructure, 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-2661 in the wild and no public exploit code.

Affected product: Oracle Financial Services Analytical Applications Infrastructure. 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-2661/ (Markdown: https://insights.sbomify.com/CVE-2018-2661/index.md)
```

## Sources

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

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