CVE-2025-50075: Oracle Financial Services Revenue Management and Billing · Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to
Affects Oracle Financial Services Revenue Management and BillingSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Mavencom.oracle.financialservices/revenue-management-billingpkg:maven/com.oracle.financialservices/revenue-management-billingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Apply official patches or updates from Oracle as soon as they are released to address CVE-2025-50075. 2. Until patches are available, restrict network access to the Oracle Financial Services Revenue Management and Billing application, especially limiting HTTP access to trusted internal networks only. 3. Implement strict network segmentation and firewall rules to isolate the affected systems from untrusted networks. 4. Enforce strong authentication and access controls to minimize the risk of low privileged accounts being compromised or misused. 5. Monitor logs and network traffic for unusual access patterns or attempts to exploit the vulnerability, focusing on HTTP requests targeting the vulnerable component. 6. Conduct regular security assessments and penetration tests to identify any residual risks related to this vulnerability. 7. Educate system administrators and security teams about the vulnerability and ensure incident response plans include scenarios involving unauthorized data access in financial systems. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block exploitation attempts targeting this vulnerability.
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 low 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 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).