CVE-2026-46808
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). The supported version that is affected is 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 14.1.2.0.0 Content Server component. Low-privileged attacker with network access can exploit this easily, requiring human interaction. Allows unauthorized creation, deletion, or modification of critical data, plus unauthorized access to critical or all accessible data. Scope change indicates attack may impact additional products beyond WebCenter Content.
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= 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.
-
Confirm Oracle WebCenter Content installationCheck for the presence of Oracle WebCenter Content on the system by reviewing installed software, Oracle inventory files, or the Content Server web interface. Common locations include the Oracle Middleware home directory or the Content Server instance directory.Affected if Oracle WebCenter Content is installed on the system
-
Verify the exact installed versionAccess the Content Server administration interface or check version files within the WebCenter Content installation directory. The version is typically displayed in the About page or can be retrieved via command line tools such as 'opatch lsinventory' or by examining the system information within the Content Server console.Affected if The installed version is exactly 14.1.2.0.0
-
Determine network accessibility of Content ServerReview network configuration to determine if the Content Server web interface (typically on ports 80, 443, or custom ports) is exposed to the network. Check firewall rules, load balancer configurations, and reverse proxy settings that control access to the Content Server.Affected if Content Server is reachable over the network from untrusted locations
-
Identify user account configurationReview the Content Server user management configuration to determine if low-privileged accounts exist. Check if the server allows authentication for users with limited permissions who could potentially exploit the vulnerability.Affected if Low-privileged user accounts are enabled and can authenticate to the Content Server
-
Check for human-interaction-dependent functionsIdentify functions within Content Server that require human interaction, such as certain workflow approvals, document check-in with manual review, or web-based forms that depend on user clicks. Review enabled Content Server features and workflows.Affected if Features or workflows requiring human interaction are enabled and accessible to low-privileged users
The environment is affected if Oracle WebCenter Content version 14.1.2.0.0 is installed and the Content Server is network-accessible with low-privileged user accounts or human-interaction-dependent functions enabled.
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 Critical Patch Update for WebCenter Content 14.1.2.0.0. Restrict network access to Content Server and disable or monitor functions requiring human interaction until patch is applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46808 — 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-46808 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