dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-46777

CRITICAL · 9.1 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 unauthenticated attacker with network access via HTTP to compromise Oracle WebCenter Content. 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 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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

Unauthenticated remote vulnerability in Oracle WebCenter Content Server allows attackers via HTTP to create, delete, or modify critical data without credentials. The flaw enables complete compromise of content data integrity and confidentiality due to missing authentication checks in the Content Server component.

MitigationApply Oracle Critical Patch Update for affected versions 12.2.1.4.0 and 14.1.2.0.0 immediately; restrict network exposure of Content Server until patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify if Oracle WebCenter Content is installed
    Look for Oracle WebCenter Content installation directories, typically under $ORACLE_HOME/Middleware/ or check for the 'ucm' or 'content' service processes on the server. Oracle WebCenter Content is often installed as part of Oracle Fusion Middleware.
    Affected if The product is present on the system.
  2. Determine the installed Content Server version
    Check the Content Server version through the Oracle Enterprise Manager console, the Content Server administration interface, or look for version files in the installation directory under Oracle_WC_Content/ucm/cs/. The affected versions are exactly 12.2.1.4.0 and exactly 14.1.2.0.0.
    Affected if The installed version matches 12.2.1.4.0 or 14.1.2.0.0 exactly.
  3. Verify Content Server HTTP network exposure
    Determine if the Content Server web interface (typically on ports 16200, 16250, or custom ports) is accessible over HTTP from untrusted networks. Check firewall rules, load balancer configurations, and the Content Server web layer binding settings.
    Affected if Content Server is reachable via HTTP from networks other than trusted administrative networks.
  4. Confirm Content Server component is enabled
    Verify that the Content Server component is active and running. Check the WebCenter Content domain configuration and ensure the 'Content Server' service is in a running state. This component must be enabled for the vulnerability to be exploitable.
    Affected if Content Server component is running and processing HTTP requests.

A system is affected if Oracle WebCenter Content versions 12.2.1.4.0 or 14.1.2.0.0 are installed with Content Server exposed via HTTP, allowing unauthenticated attackers to modify content data.

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 for affected versions 12.2.1.4.0 and 14.1.2.0.0 immediately; restrict network exposure of Content Server until patch is applied.

Fix this in Webcenter Content Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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