CVE-2026-35324
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 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 confidenceOracle WebCenter Content Content Server contains a vulnerability exploitable via HTTP by low-privileged attackers, allowing complete takeover of the content management system. The CVSS 3.1 vector indicates network-based attack with low complexity and no user interaction required, affecting versions 12.2.1.4.0 and 14.1.2.0.0.
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.
-
Verify Oracle WebCenter Content is installedCheck for the presence of Oracle WebCenter Content installation by looking for the Content Server component in Oracle inventory, or access the WebCenter Content administration console at the typical path /idc/ or check for the 'Oracle Content Server' Windows service or Unix processAffected if The product is not installed, this CVE does not apply
-
Determine Content Server versionLog into the WebCenter Content administration interface and navigate to Administration > System Information, or query the Content Server directly via the system information service endpoint, or check Oracle Inventory files for the exact installed version numberAffected if The installed version cannot be determined or the product is not present
-
Confirm exact version matches affected releasesCompare the identified version against the affected versions 12.2.1.4.0 and 14.1.2.0.0 - note these are exact version matches, not rangesAffected if The installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0, indicating the environment is vulnerable
-
Verify HTTP-based attack surface is accessibleConfirm that the Content Server HTTP/HTTPS listener is enabled and network-accessible by testing connectivity to the Content Server web ports (default 16200/16400) and verifying the IdcService endpoint respondsAffected if The HTTP interface is exposed and accessible over the network, creating the attack vector for this vulnerability
Your environment is affected ONLY if Oracle WebCenter Content Server is installed AND the installed version is exactly 12.2.1.4.0 or exactly 14.1.2.0.0 AND the HTTP interface is network-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.
From vendor dataApply the Oracle Critical Patch Update addressing this vulnerability or upgrade to a patched version of WebCenter Content. Prior to implementation, conduct a full backup and test in a non-production environment due to potential impact on content server functionality.
- Consultation8.0 h
- Implementation12.0 h
- Testing24.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 $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35324 — 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-35324 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