# CVE-2025-61884: Oracle E-Business Suite Server-Side Request Forgery (SSRF)

> Unauthenticated attackers can exploit Server-Side Request Forgery in Oracle Configurator to access critical data via HTTP.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 20 Oct 2025 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2025
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-rcj9-qvh8-q3c8

## What is CVE-2025-61884?

CVE-2025-61884 is a high-severity server-side request forgery vulnerability in Oracle Configurator, published on 12 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Configurator product of Oracle E-Business Suite (component: Runtime UI).  Supported versions that are affected are 12.2.3-12.2.14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Configurator.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Configurator accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-918 (Server-Side Request Forgery), CWE-501 (Trust Boundary Violation), CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-93 (Improper Neutralization of CRLF Sequences), CWE-287 (Improper Authentication), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-61884?

It affects 1 product.


Products: Oracle Configurator.

## How do I fix CVE-2025-61884?

No fix has been published for CVE-2025-61884 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Nov 2025.

## Is CVE-2025-61884 being exploited?

Yes. Attackers have exploited CVE-2025-61884 in the wild since at least 20 Oct 2025, including in ransomware campaigns.

Public exploit code:

- CVE-2025-61884 (github_poc): https://github.com/JrExploit/Blackash-CVE-2025-61884
- Oracle E-Business Suite - Server-Side Request Forgery (nuclei): http/cves/2025/CVE-2025-61884.yaml

## Other vulnerabilities in Oracle Configurator

- [CVE-2021-2078](https://insights.sbomify.com/CVE-2021-2078/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2021-2079](https://insights.sbomify.com/CVE-2021-2079/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2021-2080](https://insights.sbomify.com/CVE-2021-2080/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2020-14669](https://insights.sbomify.com/CVE-2020-14669/): Cross-site scripting in Configurator (high 8.2)
- [CVE-2016-3438](https://insights.sbomify.com/CVE-2016-3438/): Cross-site scripting in n/a (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61884 and fix it if it is affected.

What it is: CVE-2025-61884 is a high-severity server-side request forgery vulnerability in Oracle Configurator, published on 12 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-61884 in the wild since at least 20 Oct 2025, including in ransomware campaigns.

Affected product: Oracle Configurator. 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-2025-61884/ (Markdown: https://insights.sbomify.com/CVE-2025-61884/index.md)
```

## Sources

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

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