dbcve.org
Webcenter PortalApplication · Oracle

CVE-2026-46803

CRITICAL · 10.0 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 Portal product of Oracle Fusion Middleware (component: Security Framework). 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 Portal. While the vulnerability is in Oracle WebCenter Portal, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Portal. CVSS 3.1 Base Score 10.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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

Unauthenticated HTTP vulnerability in Oracle WebCenter Portal's Security Framework allows remote attackers to completely compromise the affected system. The flaw enables full takeover due to complete loss of confidentiality, integrity, and availability on the CVSS scale.

MitigationApply Oracle Critical Patch Updates for WebCenter Portal versions 12.2.1.4.0 and 14.1.2.0.0 when available; until then, restrict network exposure to the HTTP interface and monitor for indicators of compromise.

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 PortalApplication
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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Portal version
    Locate the installation directory and check the version file, typically in the Oracle middleware home under Oracle_WC1. Look for a version file or check the product manifest. Alternatively, access the WebCenter Portal administration console and view the About or Version information page.
    Affected if Installed version equals exactly 12.2.1.4.0 or 14.1.2.0.0
  2. Verify HTTP interface exposure
    Determine if the WebCenter Portal HTTP or HTTPS listener is accessible from network locations outside the trusted environment. Check the Oracle HTTP Server or WebLogic Server configuration for the WebCenter Portal endpoint bindings and their listen addresses.
    Affected if The HTTP interface is bound to a publicly accessible IP address or an IP address outside the trusted network segment
  3. Confirm Security Framework module is enabled
    Verify that the Security Framework component within WebCenter Portal is active. This can be done by reviewing the WebCenter Portal configuration through the Enterprise Manager Fusion Middleware Control console or by checking the deployed web application configuration files for Security Framework servlet mappings.
    Affected if The Security Framework module is deployed and accessible via HTTP
  4. Inspect access logs for unauthorized requests
    Review the Oracle WebLogic access logs and HTTP server logs for the WebCenter Portal application. Look for unusual patterns such as high volumes of requests to Security Framework endpoints, requests from unexpected source IP addresses, or authentication bypass indicators.
    Affected if Evidence of unauthenticated requests targeting Security Framework endpoints is found in the logs

A user is affected if their Oracle WebCenter Portal installation is version 12.2.1.4.0 or 14.1.2.0.0 AND the HTTP interface is exposed to untrusted networks, allowing unauthenticated attackers to reach the Security Framework.

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 Updates for WebCenter Portal versions 12.2.1.4.0 and 14.1.2.0.0 when available; until then, restrict network exposure to the HTTP interface and monitor for indicators of compromise.

Fix this in Webcenter Portal Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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