dbcve.org
Financial Services Revenue Management And BillingApplication · Oracle

CVE-2025-50075

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-21
Fix available
A fix is available. Upgrade to after 7.2.0.0.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an information disclosure vulnerability in the Security Management System component of Oracle Financial Services Revenue Management and Billing, affecting versions 2.9.0.0.0 through 7.2.0.0.0. A low-privileged attacker with network access via HTTP can exploit this to gain unauthorized access to critical or all accessible data within the application, resulting in high confidentiality impact.

MitigationApply the applicable Oracle patch for this vulnerability (refer to Oracle Critical Patch Update advisories). Review and restrict user privileges in the Security Management System, and implement network-level access controls to limit exposure to only trusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Financial Services Revenue Management And BillingApplication
Affected:>= 2.9.0.0.0, <= 7.2.0.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle Financial Services Revenue Management and Billing is installed
    Locate the application installation directory or check application server (WebLogic) deployments for Oracle Financial Services Revenue Management and Billing components. Look for application WAR files, deployment descriptors, or installation logs containing 'Oracle Financial Services' or 'Revenue Management and Billing'.
    Affected if The product is not installed or has been removed entirely.
  2. Identify the installed version number
    Check the application version by examining the deployment descriptors, version manifest files, or the application's 'About' page within the admin console. Common locations include: WEB-INF/manifest.mf, META-INF/MANIFEST.MF, or the application's main properties/configuration files that store the release version.
    Affected if The installed version falls within the range 2.9.0.0.0 through 7.2.0.0.0 (inclusive). Versions below 2.9.0.0.0 or above 7.2.0.0.0 are not affected.
  3. Verify Security Management System component is in use
    Review the application's enabled modules, features, or menu configurations to determine if the Security Management System component is active. This may be visible in the application's module configuration, feature flags, or administration console under system configuration.
    Affected if The Security Management System component is enabled and accessible within the application.
  4. Check network accessibility to HTTP endpoints
    Determine if the application HTTP/HTTPS ports are exposed to untrusted networks. Review network firewall rules, load balancer configurations, or reverse proxy settings that control access to the application URLs. Test connectivity to common application endpoints from external networks if permitted.
    Affected if The application HTTP interface is reachable from untrusted or outside networks without adequate access controls.

You are affected if Oracle Financial Services Revenue Management and Billing is installed with a version between 2.9.0.0.0 and 7.2.0.0.0, the Security Management System component is enabled, and the HTTP interface is accessible to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.2.0.0.0
Interim mitigation

Apply the applicable Oracle patch for this vulnerability (refer to Oracle Critical Patch Update advisories). Review and restrict user privileges in the Security Management System, and implement network-level access controls to limit exposure to only trusted sources.

Fix this in Financial Services Revenue Management And Billing Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-50075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-50075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data