dbcve.org
Bi PublisherApplication · Oracle

CVE-2025-61754

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 BI Publisher product of Oracle Analytics (component: Web Service API). Supported versions that are affected are 7.6.0.0.0 and 8.2.0.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle BI Publisher 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 · high confidence

Oracle BI Publisher Web Service API contains a vulnerability allowing low-privileged attackers with network access via HTTP to gain unauthorized access to critical data. The CVSS vector indicates network-based attack with low complexity, requiring only low privileges and no user interaction, resulting in high confidentiality impact.

MitigationApply the Oracle Critical Patch Update for CVE-2025-61754 to affected versions 7.6.0.0.0 and 8.2.0.0.0. As a temporary measure, restrict network access to the Web Service API endpoint and enforce strong authentication.

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
Bi PublisherApplication
Affected:= 7.6.0.0.0= 8.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. Identify Oracle BI Publisher installed version
    Check the installed version of Oracle BI Publisher in the system. This can typically be found in the Oracle BI administration console, about page, or version information file within the Oracle BI installation directory.
    Affected if The installed version is exactly 7.6.0.0.0 or exactly 8.2.0.0.0
  2. Locate the Web Service API endpoint
    Identify if the Oracle BI Publisher Web Service API endpoint is configured and accessible. Check the Oracle BI Publisher configuration files or administration settings for Web Service API endpoint definitions.
    Affected if The Web Service API endpoint is enabled and accessible in the environment
  3. Verify network accessibility of the Web Service API
    Determine if the Web Service API is reachable over network via HTTP. This can be done by checking network configuration, firewall rules, or attempting a network request to the known Web Service API URL path.
    Affected if The Web Service API is exposed to network access without proper restriction
  4. Confirm low-privileged user access exists
    Check if there are any user accounts with low privileges configured in Oracle BI Publisher that have network-accessible authentication to the system.
    Affected if Low-privileged users exist with network-accessible authentication to the Oracle BI Publisher

A user is affected if they are running exactly version 7.6.0.0.0 or 8.2.0.0.0 of Oracle BI Publisher with the Web Service API exposed to network access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update for CVE-2025-61754 to affected versions 7.6.0.0.0 and 8.2.0.0.0. As a temporary measure, restrict network access to the Web Service API endpoint and enforce strong authentication.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-61754 — 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-61754 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