dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-35325

HIGH · 8.8 CVSS v3.1 Published 2026-06-17
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

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. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle WebCenter Content. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Content. 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

Unspecified vulnerability in Oracle WebCenter Content's Content Server component allowing low-privileged attackers to achieve full system compromise via HTTP. Affects versions 12.2.1.4.0 and 14.1.2.0.0 with complete confidentiality, integrity, and availability impact.

MitigationApply Oracle Critical Patch Update when available; until then, restrict network access to Content Server to trusted IPs only and monitor for anomalous HTTP requests.

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
    Locate the Oracle WebCenter Content installation directory or check for the Content Server process running on the system. Common installation paths include Oracle middleware home directories.
    Affected if Oracle WebCenter Content Content Server is installed and running
  2. Determine Content Server version
    Access the Content Server administration interface or check version files in the installation directory. The version is typically displayed in the About page or can be retrieved via the Content Server's version information.
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  3. Verify HTTP interface is enabled
    Check if the Content Server HTTP listener is active by examining the configuration files (such as config.cfg or oc4j configurations) or by attempting to access the server on typical HTTP ports (default 80/443 or configured ports).
    Affected if HTTP access to Content Server is enabled and exposed over the network
  4. Review network exposure
    Examine firewall rules, load balancer configurations, or network ACLs to determine if the Content Server HTTP port is accessible from untrusted networks.
    Affected if Content Server HTTP interface is reachable from networks outside the trusted internal network

A system is affected if Oracle WebCenter Content Server version 12.2.1.4.0 or 14.1.2.0.0 is running with its HTTP interface exposed to potentially untrusted networks.

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 Critical Patch Update when available; until then, restrict network access to Content Server to trusted IPs only and monitor for anomalous HTTP requests.

Recommended fix Moderate confidence

Apply the relevant Oracle Critical Patch Update (CPU) for Oracle WebCenter Content that includes the fix for CVE-2026-35325; contact Oracle Support for the specific patch number and version

  1. Contact Oracle Support to obtain the Critical Patch Update (CPU) that addresses CVE-2026-35325 for Oracle WebCenter Content
  2. Apply the latest Oracle Fusion Middleware Critical Patch Update that includes the fix for this vulnerability
  3. After patching, verify the patch was applied successfully by reviewing the Oracle OPatch output
  4. Validate that the Content Server component is functioning normally post-patch
Caveat Standard Oracle CPU patching has minimal risk but requires downtime for the WebCenter Content instance during patch application; test in non-production environment first

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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