dbcve.org
Webcenter Enterprise CaptureApplication · Oracle

CVE-2026-60457

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 Enterprise Capture product of Oracle Fusion Middleware (component: Client Bundle). 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 Oracle WebCenter Enterprise Capture. While the vulnerability is in Oracle WebCenter Enterprise Capture, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Enterprise Capture. 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 · moderate confidence

Deserialization vulnerability in Oracle WebCenter Enterprise Capture's Client Bundle component allows low-privileged attackers to achieve remote code execution via T3/IIOP protocols. The vulnerability enables complete system compromise (confidentiality, integrity, availability) and represents a scope change where exploitation of this component can impact additional Oracle products.

MitigationApply Oracle Critical Patch Update patches for WebCenter Enterprise Capture or upgrade to a patched version; restrict T3/IIOP network access at the infrastructure level if patching is immediately infeasible.

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 Enterprise CaptureApplication
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 installed WebCenter Enterprise Capture version
    Locate the Oracle WebCenter Enterprise Capture installation directory and check the version manifest or inventory file. Common locations include the ORACLE_HOME directory under Capture folder. Use Oracle Fusion Middleware inventory commands (like 'opatch lsinventory') if available.
    Affected if Installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  2. Verify T3 protocol listener is enabled
    Check WebLogic Server configuration for T3 protocol listeners. Inspect the WebLogic Administration Console or config.xml for network channel definitions listening on T3 protocol. Look for entries with 't3' in the protocol or channel configuration.
    Affected if T3 protocol listener is active and configured on any network channel
  3. Verify IIOP protocol listener is enabled
    Check WebLogic Server configuration for IIOP protocol listeners. Inspect the WebLogic Administration Console or config.xml for IIOP-enabled object URLs. Look for 'iiop' in protocol settings or IIOP service enabled flags.
    Affected if IIOP protocol listener is active and configured
  4. Check network exposure of T3/IIOP ports
    Review firewall rules and WebLogic network channel bindings to determine which network interfaces and ports are listening for T3/IIOP traffic. Identify if ports are bound to external-facing interfaces versus localhost only.
    Affected if T3/IIOP ports are accessible from network segments beyond localhost or trusted internal networks

Environment is affected if WebCenter Enterprise Capture version is exactly 12.2.1.4.0 or 14.1.2.0.0 AND T3 or IIOP protocols are enabled and accessible on 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 Critical Patch Update patches for WebCenter Enterprise Capture or upgrade to a patched version; restrict T3/IIOP network access at the infrastructure level if patching is immediately infeasible.

Fix this in Webcenter Enterprise Capture Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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