dbcve.org
Weblogic ServerApplication · Oracle

CVE-2025-61764

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 WebLogic Server product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0 and 14.1.2.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WebLogic Server contains an information disclosure vulnerability in its Core component. Unauthenticated remote attackers can exploit this via HTTP to gain unauthorized read access to a subset of accessible data. The attack is low complexity, requires no authentication, and targets confidentiality only.

MitigationApply Oracle's available patches for WebLogic Server versions 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0. Restrict HTTP/HTTPS access to WebLogic Server administrative interfaces to trusted networks if immediate patching is not feasible.

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
Weblogic ServerApplication
Affected:= 12.2.1.4.0= 14.1.1.0.0= 14.1.2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WebLogic Server installation and version
    Check for WebLogic Server installation directories (typically $ORACLE_HOME or C:\Oracle\Middleware) and locate the version file, commonly found in the registry or version.txt in the installation root. On Linux/Unix, you can also check using the WebLogic inventory or startup scripts that report version information.
    Affected if The installed version is exactly 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0
  2. Verify HTTP/HTTPS listeners are enabled
    Check if WebLogic Server is configured with HTTP or HTTPS network listeners. Review the WebLogic Server configuration files (config.xml) for <NetworkAccessPoint> or <Server> elements that define HTTP/HTTPS ports. Common default ports are 7001 for HTTP and 7002 for HTTPS.
    Affected if HTTP or HTTPS listeners are configured and accessible on any port
  3. Confirm the Core component is in use
    The Core component is the base WebLogic Server runtime and is always loaded when the server starts. Verify the WebLogic Server process is running and the Core component is active by checking the administration console or by examining the deployed applications and server runtime state.
    Affected if WebLogic Server is running with the Core component active (default state for any WebLogic installation)
  4. Assess network exposure of WebLogic endpoints
    Review firewall rules, load balancer configurations, or network ACLs that control access to the WebLogic HTTP/HTTPS ports. Determine if the WebLogic administration console (usually on port 7001/7002) or HTTP channels are reachable from untrusted networks.
    Affected if WebLogic HTTP/HTTPS ports are accessible from untrusted or external network segments

Your environment is affected if you are running WebLogic Server version 12.2.1.4.0, 14.1.1.0.0, or 14.1.2.0.0 with HTTP/HTTPS listeners exposed to the network where unauthenticated attackers could reach them.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's available patches for WebLogic Server versions 12.2.1.4.0, 14.1.1.0.0, and 14.1.2.0.0. Restrict HTTP/HTTPS access to WebLogic Server administrative interfaces to trusted networks if immediate patching is not feasible.

Recommended fix Moderate confidence

Apply Oracle CPU (Critical Patch Update) containing the fix for CVE-2025-61764

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2025-61764. Oracle releases security patches on a quarterly cycle (January, April, July, October).
  2. Download the latest Oracle Critical Patch Update from Oracle Support (support.oracle.com) or Oracle's official security alerts page.
  3. Review the README.txt file included with the patch for specific installation instructions for WebLogic Server.
  4. Ensure you have a complete backup of your WebLogic Server installation and domain configuration before applying the patch.
  5. Stop all WebLogic Server processes and Node Manager before applying the patch.
  6. Apply the patch using Oracle's Opatch utility: opatch apply.
  7. Restart the WebLogic Server processes after the patch is successfully applied.
  8. Verify the patch was installed correctly by running: opatch lsinventory.
Caveat Oracle CPU patches typically include multiple security fixes and may require testing; review patch readme for any known issues or required configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Weblogic Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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