CVE-2025-21573: Oracle Financial Services Revenue Management and Billing · Difficult to exploit vulnerability allows high 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.0 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 15 Apr 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/financial-services-revenue-management-and-billingpkg:maven/com.oracle/financial-services-revenue-management-and-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
Organizations should implement the following specific mitigations: 1) Monitor and restrict network access to Oracle Financial Services Revenue Management and Billing HTTP interfaces, limiting exposure to trusted networks and users. 2) Enforce strict access control policies to ensure only authorized high-privileged users have access, and regularly review user privileges. 3) Conduct user awareness training to reduce the risk of social engineering attacks that could trigger the required user interaction. 4) Implement robust logging and monitoring to detect unusual activities related to data modification or access. 5) Apply any available Oracle patches or security updates promptly once released. 6) Consider deploying web application firewalls (WAFs) with custom rules to detect and block suspicious HTTP requests targeting the Chatbot component. 7) Segment the network to isolate critical financial systems and reduce lateral movement opportunities. 8) Perform regular security assessments and penetration testing focused on the Oracle Financial Services environment to identify potential exploitation paths.
Description
Vulnerability in the Oracle Financial Services Revenue Management and Billing product of Oracle Financial Services Applications (component: Chatbot). Supported versions that are affected are 5.1.0.0.0, 6.1.0.0.0 and 7.0.0.0.0. Difficult to exploit vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Financial Services Revenue Management and Billing. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Financial Services Revenue Management and Billing accessible data as well as unauthorized access to critical data or complete access to all Oracle Financial Services Revenue Management and Billing accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Financial Services Revenue Management and Billing. CVSS 3.1 Base Score 6.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:L).