dbcve.org
Webcenter ContentApplication · Oracle

CVE-2026-46804

HIGH · 8.7 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 →
91/100
Remediation priority · Urgent
Remotely reachable

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). The supported version that is affected is 14.1.2.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle WebCenter Content. Successful attacks require human interaction from a person other than the attacker and 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.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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

A vulnerability in Oracle WebCenter Content's Content Server (version 14.1.2.0.0) allows low-privileged attackers with network access via HTTP to compromise the system. The flaw enables unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to sensitive or all accessible data. Exploitation requires human interaction and can impact additional products beyond the vulnerable component due to scope change.

MitigationApply Oracle's official security patches for WebCenter Content 14.1.2.0.0 when available. In the interim, restrict network access to Content Server, enforce least-privilege user permissions, and monitor for suspicious administrative actions.

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:= 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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Identify Oracle WebCenter Content installation
    Locate the Content Server installation directory or check running processes for Oracle WebCenter Content components. Common paths include Oracle middleware home directories or check the process list for Content Server Java processes.
    Affected if Oracle WebCenter Content Content Server is found running on the system
  2. Verify exact version number
    Check the installed Content Server version. Access the About page via the web interface, check the ORACLE_HOME/wccontent directory for version files, or query the system using the Oracle Enterprise Manager console if available.
    Affected if The installed version is exactly 14.1.2.0.0
  3. Confirm HTTP network accessibility
    Determine if the Content Server web interface (typically on ports 80, 443, 8080, or 8443) is exposed to the network. Check firewall rules, load balancer configurations, or test external connectivity to the HTTP endpoints.
    Affected if The Content Server HTTP interface is accessible over the network to untrusted users
  4. Verify low-privileged user access
    Review the Content Server user database and authentication configuration. Check if low-privileged or standard user accounts exist and can authenticate to the system via the HTTP interface.
    Affected if Low-privileged user accounts can authenticate to the Content Server HTTP interface

The system is affected if it runs exactly Oracle WebCenter Content version 14.1.2.0.0 with its HTTP interface network-accessible to low-privileged users.

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's official security patches for WebCenter Content 14.1.2.0.0 when available. In the interim, restrict network access to Content Server, enforce least-privilege user permissions, and monitor for suspicious administrative actions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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