dbcve.org
Webcenter SitesApplication · Oracle

CVE-2026-46799

CRITICAL · 9.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 →
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 Sites product of Oracle Fusion Middleware (component: WebCenter Sites). 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 Sites. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Sites. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 · high confidence

Unauthenticated remote code execution vulnerability in Oracle WebCenter Sites allows unauthenticated attackers with network access via HTTP to achieve full system compromise and takeover of the affected WebCenter Sites installation.

MitigationApply Oracle Critical Patch Update addressing CVE-2026-46799; until patch is available, restrict network access to WebCenter Sites HTTP endpoints and implement additional authentication layers.

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 SitesApplication
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
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Sites installation
    Locate WebCenter Sites by checking for Oracle WebLogic Server deployments or looking for 'wcsites' or 'WebCenter Sites' directories in the Oracle middleware home directory (typically $ORACLE_HOME/wc_sites or similar). Verify the application is running by accessing the WebCenter Sites login or administration URLs.
    Affected if Oracle WebCenter Sites is not found in the environment, the system is not affected.
  2. Determine the installed WebCenter Sites version
    Access the WebCenter Sites Admin interface or check version files in the installation directory. The version is typically displayed on the login page or in the About section of the administration console. Alternatively, check deployment descriptors or manifest files in the application WAR/EAR files.
    Affected if The installed version is exactly 12.2.1.4.0 or 14.1.2.0.0, proceed to network exposure check.
  3. Verify HTTP network exposure of WebCenter Sites
    Confirm that the WebCenter Sites HTTP endpoints are accessible over the network. Check if the application listens on HTTP (port 80/443 or WebLogic HTTP port) and is reachable from external or untrusted networks. Use network scanning tools or review firewall/load balancer configurations.
    Affected if HTTP endpoints are exposed to untrusted networks without proper access restrictions, the system is vulnerable to unauthenticated exploitation.
  4. Check for existing authentication enforcement
    Review the WebCenter Sites configuration to confirm that authentication is required for accessing the application. Verify that anonymous or unauthenticated access is not enabled for critical endpoints. Check WebLogic security realm settings and WebCenter Sites security configurations.
    Affected if The application allows unauthenticated access via HTTP, the vulnerability is exploitable.

A system is affected if it runs Oracle WebCenter Sites version 12.2.1.4.0 or 14.1.2.0.0 with HTTP endpoints exposed to network access without proper authentication restrictions.

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 addressing CVE-2026-46799; until patch is available, restrict network access to WebCenter Sites HTTP endpoints and implement additional authentication layers.

Fix this in Webcenter Sites Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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