dbcve.org
EssbaseApplication · Oracle

CVE-2025-61763

HIGH · 8.1 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 →
87/100
Remediation priority · High
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 Oracle Essbase (component: Essbase Web Platform). The supported version that is affected is 21.7.3.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Essbase. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Essbase accessible data as well as unauthorized access to critical data or complete access to all Oracle Essbase accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Essbase Web Platform contains an authorization flaw allowing low-privileged authenticated users to gain unauthorized access to critical data and perform unauthorized creation, deletion, or modification operations via HTTP requests. The vulnerability is easily exploitable over the network with low complexity and requires no user interaction.

MitigationApply the Oracle Critical Patch Update when available. Until patch deployment, restrict network access to Essbase Web Platform to trusted users only and monitor for unauthorized data access or modification attempts.

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
EssbaseApplication
Affected:= 21.7.3.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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Locate Oracle Essbase installation
    Search for Essbase installation directories: on Linux/Unix check /opt/oracle, /u01, /app; on Windows check C:\oracle, C:\Oracle. Look for folders named 'essbase' or 'products' containing Essbase.
    Affected if Oracle Essbase is not installed on the system - no further action needed.
  2. Identify installed Essbase version
    Check for version file in the installation directory. Common locations: <ORACLE_HOME>/essbase/version.txt, or look in <ORACLE_HOME>/inventory/ContentsXML/oracle_comps.xml. Alternatively, run 'opatch lsinventory' if OPatch is configured.
    Affected if The installed version is exactly 21.7.3.0.0 - proceed to next checks.
  3. Confirm Web Platform component status
    Check if the Web Platform (Essbase Web Interface) is deployed and running. Look for web application archives in <ORACLE_HOME>/user_projects/domains/<domain>/servers or check the Oracle Enterprise Manager console for deployed web applications.
    Affected if Web Platform interface is accessible and running on the server.
  4. Verify network accessibility of Web Platform
    Check if the Web Platform HTTP port is exposed externally. Review firewall rules, load balancer configurations, or the httpd.conf/oid.conf for exposed listeners. Default ports for Essbase Web are typically 7000-9000 range.
    Affected if Web Platform port is accessible from untrusted networks or non-admin users.

You are affected if Oracle Essbase version 21.7.3.0.0 is installed and the Web Platform component is network-accessible to low-privileged users.

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 when available. Until patch deployment, restrict network access to Essbase Web Platform to trusted users only and monitor for unauthorized data access or modification attempts.

Fix this in Essbase Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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