dbcve.org
Webcenter PortalApplication · Oracle

CVE-2026-60565

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 4 weeks old

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 WebCenter Portal product of Oracle Fusion Middleware (component: Runtime Tools). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle WebCenter Portal. While the vulnerability is in Oracle WebCenter Portal, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Portal. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

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

Critical vulnerability in Oracle WebCenter Portal's Runtime Tools component allows low-privileged attackers with network access via HTTP to achieve complete compromise of the portal, including full confidentiality, integrity, and availability impact. The CVSS vector indicates a scope change, meaning attacks may significantly impact additional products beyond Oracle WebCenter Portal.

MitigationApply Oracle's security patches for the affected versions (12.2.1.4.0 and 14.1.2.0.0) as soon as Oracle publishes them. Until a patch is available, restrict network access to the WebCenter Portal interfaces to minimize attack surface.

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
Webcenter PortalApplication
Affected:= 12.2.1.4.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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 if Oracle WebCenter Portal is installed
    Check for WebCenter Portal installation directories (typically under $ORACLE_HOME/webcenter or similar Oracle Middleware paths) or query the Oracle inventory. On Windows, check Program Files for Oracle middleware installations.
    Affected if Oracle WebCenter Portal software is present on the system
  2. Determine the installed WebCenter Portal version
    Locate the version file in the WebCenter Portal installation directory, typically in OPatch or inventory files, or access the WebCenter Portal administration console and navigate to About/Version information.
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  3. Verify if Runtime Tools component is configured
    Check the WebCenter Portal configuration files (such as webcenter-config.xml or corresponding deployment descriptors) for the Runtime Tools module or feature enablement, or access the WebCenter Portal administration console to view enabled components.
    Affected if Runtime Tools component is present and enabled in the WebCenter Portal configuration
  4. Check network exposure of Runtime Tools endpoints
    Review web server or load balancer configurations, firewall rules, and Oracle WebLogic Server deployment descriptors to determine if Runtime Tools HTTP endpoints are accessible from the network. Common paths include /runtime-tools/ or similar patterns under the WebCenter context.
    Affected if Runtime Tools endpoints are exposed via HTTP/HTTPS to network users

A user is affected if they have Oracle WebCenter Portal versions 12.2.1.4.0 or 14.1.2.0.0 installed with the Runtime Tools component enabled and accessible over the network.

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 Oracle's security patches for the affected versions (12.2.1.4.0 and 14.1.2.0.0) as soon as Oracle publishes them. Until a patch is available, restrict network access to the WebCenter Portal interfaces to minimize attack surface.

Fix this in Webcenter Portal Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
38.0 hours of engineering $6,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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