dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-60465

HIGH · 8.8 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 →
94/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 WebCenter Content: Imaging product of Oracle Fusion Middleware (component: Core). 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 T3, IIOP to compromise WebCenter Content: Imaging. Successful attacks of this vulnerability can result in takeover of WebCenter Content: Imaging. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 · moderate confidence

Oracle WebCenter Content: Imaging contains a vulnerability in its Core component that allows authenticated attackers with network access via T3 or IIOP protocols (Oracle WebLogic communication protocols) to achieve complete system compromise. The CVSS vector indicates low privilege requirements and network-based attack vector, making it easily exploitable.

MitigationRestrict network access to WebCenter Content: Imaging systems and disable T3/IIOP protocols if not required for business operations. Apply Oracle patches when available and audit user privileges.

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 ContentApplication
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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 Oracle WebCenter Content installation
    Look for the WebCenter Content installation directory (typically under Oracle middleware home) or check for running processes named 'ContentServer', 'Oracle WebCenter Content', or associated Java processes
    Affected if Oracle WebCenter Content is not installed on the system
  2. Check installed WebCenter Content version
    Navigate to the Content Server installation directory and locate the version file or check the About/Version information in the Content Server admin console. Common locations: <install_dir>/ucm/cs/bin or check the version.properties file
    Affected if The installed version matches 12.2.1.4.0 or 14.1.2.0.0 exactly
  3. Verify T3 protocol is enabled
    Check the WebLogic Server configuration files (config.xml) or access the WebLogic Administration Console. Look for the T3 protocol listener configuration, typically on port 7001 or configured in the Servers > <server> > General > Enable T3 checkbox
    Affected if T3 protocol is enabled and accessible on the network
  4. Verify IIOP protocol is enabled
    Check WebLogic Server configuration for IIOP. In WebLogic Administration Console, go to Servers > <server> > Protocols > IIOP. Alternatively, inspect the config.xml for <iiop> or <iiop-msg> protocol configurations
    Affected if IIOP protocol is enabled and accessible on the network

The environment is affected only if Oracle WebCenter Content versions 12.2.1.4.0 or 14.1.2.0.0 are installed AND T3 or IIOP protocols are enabled and network-accessible, as these protocols are required vectors for the deserialization attack.

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

Restrict network access to WebCenter Content: Imaging systems and disable T3/IIOP protocols if not required for business operations. Apply Oracle patches when available and audit user privileges.

Fix this in Webcenter Content Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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