CVE-2026-60561
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 · uneditedVulnerability in the Oracle WebCenter Portal product of Oracle Fusion Middleware (component: Runtime Tools). 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 confidenceA critical vulnerability in Oracle WebCenter Portal's Runtime Tools component allows a low-privileged attacker with network access via HTTP to achieve complete takeover of the portal. The CVSS 9.9 score indicates full confidentiality, integrity, and availability compromise, with attacks potentially affecting additional products due to scope change.
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= 12.2.1.4.0= 14.1.2.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle WebCenter Portal is installedLocate WebCenter Portal installation directory or check for WebCenter Portal processes running on the server. Common locations include $ORACLE_HOME/webcenter or check for Oracle Fusion Middleware components.Affected if WebCenter Portal is not installed - not affected. If installed, continue to version check.
-
Identify installed WebCenter Portal versionCheck the version of Oracle WebCenter Portal using Oracle Enterprise Manager, Fusion Middleware Control, or by examining the installation logs and configuration files. The version is typically displayed in the Fusion Middleware console or can be queried via Oracle OPatch.Affected if Version is 12.2.1.4.0 or 14.1.2.0.0 - potentially affected. Versions outside these specific releases are not affected by this CVE.
-
Verify Runtime Tools component is configuredCheck if the Runtime Tools component is enabled in the WebCenter Portal configuration. This can be verified through Fusion Middleware Control under the Runtime Tools configuration section, or by examining the component configuration XML files in the WebCenter Portal domain.Affected if Runtime Tools component is present and enabled - vulnerable attack surface exists. If Runtime Tools is not configured or disabled, the attack surface may be reduced.
-
Assess network exposure of WebCenter PortalReview network listeners and HTTP endpoints configured for WebCenter Portal. Check the Oracle HTTP Server (OHS) configuration and WebLogic Server network channels to determine what IP addresses or networks can access the portal via HTTP.Affected if WebCenter Portal is accessible via HTTP from untrusted networks - attacker with network access could attempt exploitation. Restrict access to trusted sources reduces risk.
-
Review WebCenter Portal user privilegesExamine the user accounts and roles configured in WebCenter Portal's identity store. Check for low-privilege accounts that have any portal access, as the CVE states a low-privileged attacker can achieve full takeover.Affected if Low-privilege users have portal access - these accounts could be leveraged by an attacker for exploitation. Minimizing user privileges reduces the attack chain.
Environment is affected only if Oracle WebCenter Portal versions 12.2.1.4.0 or 14.1.2.0.0 are installed, the Runtime Tools component is enabled, and the portal is accessible via HTTP to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Oracle Critical Patch Update for WebCenter Portal versions 12.2.1.4.0 and 14.1.2.0.0; if no patch is available, consider restricting network access to the Runtime Tools component and implementing additional access controls.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60561 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60561 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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