CVE-2026-60656
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 Content product of Oracle Fusion Middleware (component: Web Content Management). 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 Content. Successful attacks of this vulnerability can result in takeover of Oracle WebCenter Content. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 confidenceA critical vulnerability in Oracle WebCenter Content's Web Content Management component allows authenticated attackers with low privileges to achieve complete system takeover via HTTP requests. The attack is low complexity, requires no user interaction, and provides high impact across confidentiality, integrity, and availability.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle WebCenter Content installationLocate the Oracle WebCenter Content installation directory and confirm the product name. Typically found in $ORACLE_HOME/ucm or similar paths. Check for 'Oracle WebCenter Content' in installed software listings or documentation.Affected if Product is not Oracle WebCenter Content
-
Check installed version numberAccess the WebCenter Content Administration menu, or check the version file in the installation directory (often version.txt or about.html in the admin interface). Common paths: <install_dir>/ucm/shell、管理页面或版本信息文件。Affected if Installed version is exactly 12.2.1.4.0 or 14.1.2.0.0
-
Verify Web Content Management module is enabledLog into WebCenter Content admin interface and navigate to Server Configuration or Component Management to confirm if the Web Content Management (WCM) component is installed and active.Affected if Web Content Management module is installed and active
-
Confirm HTTP network accessibilityVerify that the WebCenter Content web interface is accessible over HTTP/HTTPS from the network. Check firewall rules, load balancer config, or test connectivity to the default port (typically 16200 or 443).Affected if HTTP interface is exposed to untrusted networks
-
Review user access and authenticationCheck if low-privileged user accounts exist in the WebCenter Content system. Review the Users and Roles configuration to confirm that accounts with limited privileges can access the WCM functionality.Affected if Low-privileged authenticated users have access to the system
User is affected if running exactly version 12.2.1.4.0 or 14.1.2.0.0 of Oracle WebCenter Content with Web Content Management enabled and accessible over HTTP to low-privileged users.
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 Oracle security patches when released; until then, restrict network access to WebCenter Content to trusted IPs only and deploy a WAF to filter malicious requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60656 — 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-60656 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