# CVE-2025-50074: Information disclosure in Oracle Financial Services Revenue Management and Billing

> A high-privileged attacker can exploit this vulnerability to gain unauthorized access to critical data in Oracle Financial Services Revenue Management and Billing.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-fpvc-v72h-gxw6

## What is CVE-2025-50074?

CVE-2025-50074 is a medium-severity vulnerability in Oracle Financial Services Revenue Management and Billing, published on 21 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle Financial Services Revenue Management and Billing product of Oracle Financial Services Applications (component: Security Management System).  Supported versions that are affected are 2.9.0.0.0-7.2.0.0.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Financial Services Revenue Management and Billing.  Successful attacks of this vulnerability can result in  unauthorized access to critical data or complete access to all Oracle Financial Services Revenue Management and Billing accessible data. CVSS 3.1 Base Score 4.9 (Confidentiality impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N).

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Oracle Financial Services Revenue Management and Billing.

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

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

## Is CVE-2025-50074 being exploited?

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

## Other vulnerabilities in Oracle Financial Services Revenue Management and Billing

- [CVE-2025-50075](https://insights.sbomify.com/CVE-2025-50075/): Missing authorization in Oracle Financial Services Revenue Management and Billing (medium 6.5)
- [CVE-2024-21188](https://insights.sbomify.com/CVE-2024-21188/): Cross-site scripting in Financial Services Revenue Management and Billing (medium 6.1)
- [CVE-2025-21573](https://insights.sbomify.com/CVE-2025-21573/): Missing authorization in Oracle Financial Services Revenue Management and Billing (medium 6.0)
- [CVE-2022-21580](https://insights.sbomify.com/CVE-2022-21580/): Information disclosure in Financial Services Revenue Management and Billing (medium 5.9)
- [CVE-2021-2113](https://insights.sbomify.com/CVE-2021-2113/): Missing authorization in Financial Services Revenue Management and Billing (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50074 is a medium-severity vulnerability in Oracle Financial Services Revenue Management and Billing, published on 21 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-50074 in the wild and no public exploit code.

Affected product: Oracle Financial Services Revenue Management and Billing. 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-50074/ (Markdown: https://insights.sbomify.com/CVE-2025-50074/index.md)
```

## Sources

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

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