dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-60525

HIGH · 8.2 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 →
88/100
Remediation priority · High
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 Content product of Oracle Fusion Middleware (component: Content Server). Supported versions that are affected are 12.2.1.4.0 and 14.1.2.0.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle WebCenter Content. While the vulnerability is in Oracle WebCenter Content, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebCenter Content accessible data as well as unauthorized access to critical data or complete access to all Oracle WebCenter Content accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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

Authenticated vulnerability in Oracle WebCenter Content's Content Server component affecting versions 12.2.1.4.0 and 14.1.2.0.0. Allows low-privileged attackers via HTTP to perform unauthorized creation, deletion, or modification of critical data, as well as access critical or complete accessible data. High exploitation complexity (AC:H) but successful attacks achieve confidentiality and integrity impacts.

MitigationApply the Oracle Critical Patch Update (CPU) containing the fix for this vulnerability. Prior to production deployment, test in a non-production environment to validate compatibility and ensure no disruption to Content Server functionality.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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. Confirm Oracle WebCenter Content is installed
    Check for the presence of Oracle WebCenter Content installation directory, or look for processes named 'ContentServer', 'UCM', or 'Oracle WebCenter Content' running on the system
    Affected if Oracle WebCenter Content server is present and running
  2. Identify the installed WebCenter Content version
    Locate the version file or check the admin console for the exact version number. Common paths include the Oracle inventory or the Content Server installation directory containing a version manifest
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  3. Verify HTTP or HTTPS network listener is enabled
    Check the Content Server configuration for active web listeners, typically in the config.cfg or via the admin interface under Server Administration > Network Settings
    Affected if HTTP or HTTPS network access is enabled and exposed
  4. Confirm the server is reachable over the network
    Attempt to access the Content Server login page or web services endpoint from a network client, or verify that the web listener is bound to a network interface
    Affected if The Content Server HTTP endpoint is network-accessible from untrusted networks

Your environment is affected if Oracle WebCenter Content versions 12.2.1.4.0 or 14.1.2.0.0 are installed with HTTP network access enabled and the server is reachable from the network where low-privileged attackers could connect.

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 (CPU) containing the fix for this vulnerability. Prior to production deployment, test in a non-production environment to validate compatibility and ensure no disruption to Content Server functionality.

Fix this in Webcenter Content 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-60525 — 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-60525 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