dbcve.org
Webcenter PortalApplication · Oracle

CVE-2026-46814

CRITICAL · 9.9 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 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 low privileged 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 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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

A critical vulnerability in the Security Framework component of Oracle WebCenter Portal allows a low-privileged attacker with network access via HTTP to achieve complete takeover of the portal, compromising confidentiality, integrity, and availability. The vulnerability affects versions 12.2.1.4.0 and 14.1.2.0.0, and due to scope change, attacks may impact additional products beyond WebCenter Portal.

MitigationApply the Oracle Critical Patch Update for this vulnerability when released; until then, restrict network access to WebCenter Portal to trusted sources only and implement additional monitoring for suspicious HTTP activity.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 WebCenter Portal installation and check the version manifest or about page. Common paths include the Oracle Middleware home directory or the portal's administration console. Alternatively, query the Oracle Enterprise Manager for the installed WebCenter Portal version.
    Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
  2. Confirm Security Framework component is deployed
    Verify that the Security Framework module is active in the WebCenter Portal deployment. This can be checked through the WebCenter Portal administration console under component status or by examining the deployed EAR/WAR file manifest.
    Affected if The Security Framework component is present and enabled in the portal configuration
  3. Assess HTTP network exposure
    Determine if WebCenter Portal is accessible over HTTP/HTTPS from the network. Review network firewall rules, load balancer configurations, and reverse proxy settings that expose the portal. Check if the port (typically 8888, 7001, or 80/443) is reachable from untrusted networks.
    Affected if WebCenter Portal HTTP endpoints are reachable from network locations outside the trusted internal network
  4. Review low-privilege user accounts
    Audit existing user accounts in WebCenter Portal with low-privilege roles (such as guest, viewer, or standard user). Check the identity store configuration and count of such accounts.
    Affected if Low-privileged user accounts exist in the system that could be leveraged for exploitation

A user is affected if their Oracle WebCenter Portal installation is version 12.2.1.4.0 or 14.1.2.0.0, has the Security Framework component enabled, and is accessible over HTTP from the network where a low-privileged account could be abused.

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 the Oracle Critical Patch Update for this vulnerability when released; until then, restrict network access to WebCenter Portal to trusted sources only and implement additional monitoring for suspicious HTTP activity.

Fix this in Webcenter Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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