CVE-2026-60443
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: Content Server). 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 require human interaction from a person other than the attacker and while the vulnerability is in Oracle WebCenter Content, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle WebCenter Content accessible data as well as unauthorized access to critical data or complete access to all Oracle WebCenter Content accessible data. CVSS 3.1 Base Score 8.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N).
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 confidenceVulnerability in Oracle WebCenter Content's Content Server component allows low privileged attackers with network access via HTTP to compromise the system. Successful exploitation requires human interaction from a person other than the attacker and enables unauthorized creation, deletion, or modification of critical data, as well as unauthorized access to critical or all accessible data. The attack results in high confidentiality and integrity impacts with a scope change affecting additional products.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
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 WebCenter Content installation directory and check for the Content Server component. Common paths include Oracle middleware home directories. Look for the 'ucm' or 'oracle_webcenter_content' directories.Affected if Oracle WebCenter Content Server is installed on the system
-
Determine installed versionCheck the version of the installed WebCenter Content Server. Typically found in product documentation, installer logs, or by accessing the About section of the Content Server administration interface.Affected if The installed version matches exactly 12.2.1.4.0 or 14.1.2.0.0
-
Verify HTTP interface is enabledConfirm that the Content Server HTTP interface is active and accessible. Check the web server configuration or attempt to access the Content Server URL on standard HTTP/HTTPS ports.Affected if HTTP interface is enabled and reachable over the network
-
Review HTTP access logs for injection patternsExamine Content Server HTTP access and error logs for unusual parameter patterns, especially in areas where user input is processed. Look for suspicious SQL-like characters, command syntax, or unexpected parameter modifications.Affected if Logs contain unusual injection-style requests or unexpected parameter modifications in HTTP requests
The environment is affected if Oracle WebCenter Content Server version 12.2.1.4.0 or 14.1.2.0.0 is installed with the HTTP interface enabled and accessible.
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.
dbcve · scopedRestrict network access to Oracle WebCenter Content servers, apply Oracle patches when available, and implement additional authentication controls. Monitor for unauthorized data access or modification patterns.
Oracle WebCenter Content 12.2.1.4.2407+ or 14.1.2.0.2407+ (latest available 12.2.1.4.x or 14.1.2.x patch bundle)
- 1. Identify the current Oracle WebCenter Content version by checking the Oracle WebCenter Content Admin Server or using the version information in the Content Server console.
- 2. Navigate to Oracle Support (support.oracle.com) and search for Oracle WebCenter Content Critical Patch Updates.
- 3. Apply the latest Oracle Critical Patch Update (CPU) that addresses CVE-2026-60443. For 12.2.1.4.0, apply the latest 12.2.1.4.x patch bundle. For 14.1.2.0.0, apply the latest 14.1.2.x patch bundle.
- 4. For Oracle WebCenter Content 12.2.1.4.0, consider upgrading to 12.2.1.4.2407 or later which includes the security fix.
- 5. For Oracle WebCenter Content 14.1.2.0.0, upgrade to 14.1.2.0.2407 or later which includes the security fix.
- 6. After applying the patch, restart the Oracle WebCenter Content Content Server and Admin Server services.
- 7. Verify the patch was applied successfully by checking the Oracle WebCenter Content patch information in the Admin Server and confirming the CVE is addressed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60443 — 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-60443 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