CVE-2026-35322: Oracle WebCenter Content Privilege Escalation (CVSS 8.8)
A privilege escalation vulnerability exists in Oracle WebCenter Content that allows an authenticated user with basic network access to gain complete administrative control of the system. The vulnerability resides in the Content Server component and affects two recent versions of the product. An attacker who already has low-level user credentials can exploit this flaw without user interaction to compromise confidentiality, integrity, and availability of the entire WebCenter Content instance.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-284
- Affected products
- 2 configuration(s)
- Published / Modified
- 2026-06-17 / 2026-06-19
NVD description (verbatim)
Vulnerability 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).
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-35322 is an improper access control vulnerability (CWE-284) in the Oracle WebCenter Content product, affecting versions 12.2.1.4.0 and 14.1.2.0.0. The vulnerability allows a low-privileged authenticated attacker to escalate privileges via HTTP network requests. The attack requires no user interaction and succeeds against the default security configuration. With a CVSS 3.1 score of 8.8 and a vector of AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, the flaw carries high impact across all three security dimensions: an attacker gains the ability to read, modify, or delete protected content; manipulate system configuration; and disrupt service availability.
Business impact
Organizations relying on Oracle WebCenter Content for enterprise document management face significant operational and security risk. A successful exploit enables attackers to exfiltrate sensitive documents, modify compliance records, inject malicious content, or destroy data integrity. For regulated industries (finance, healthcare, legal), this can result in breach notification obligations, regulatory penalties, and loss of stakeholder trust. The vulnerability is particularly concerning because it requires only standard user credentials—meaning insider threats, compromised contractor accounts, or lateral movement from other breached systems can trigger full system compromise. Remediation delays increase exposure window and potential forensic complexity.
Affected systems
Oracle WebCenter Content versions 12.2.1.4.0 and 14.1.2.0.0 are directly impacted. Organizations should immediately inventory deployments of these specific builds. Verify exact patch levels in your environment, as intermediate versions between these releases may also be affected—consult Oracle's official advisory for the complete support matrix. Environments where WebCenter Content is internet-facing or accessible to remote workers carry elevated risk. Air-gapped or heavily network-segmented deployments have reduced but not eliminated exposure if internal actors possess valid credentials.
Exploitability
This vulnerability is easily exploitable from a technical standpoint: the attack vector is network-accessible (HTTP), the attack complexity is low, and no user interaction is required. The critical limiting factor is the attacker must already possess valid low-privileged user credentials. This significantly reduces opportunistic external exploitation but does not eliminate risk. Compromised employee accounts, overly-permissive service accounts, or credentials leaked through phishing campaigns are realistic attack prerequisites. The vulnerability has not been added to CISA's Known Exploited Vulnerabilities catalog, but organizations should assume active research and eventual proof-of-concept development given the high CVSS score and ease of exploitation once initial access is obtained.
Remediation
Apply security patches from Oracle immediately upon availability. Oracle typically releases critical patches on its published Critical Patch Update (CPU) schedule or as out-of-band fixes. Until patches are deployed, implement strict network access controls: restrict HTTP access to WebCenter Content to trusted internal networks, disable remote access where operationally feasible, and enforce multi-factor authentication for all user accounts. Review and revoke unnecessary user privileges, particularly service accounts and administrative roles. Monitor access logs for anomalous activity, especially privilege escalation attempts and bulk content downloads. Isolate vulnerable instances from production workflows if patches cannot be applied within your maintenance window.
Patch guidance
Contact Oracle Support or consult the Oracle Security Alerts page for patch availability and version-specific guidance. Patches will be version-specific; do not assume a patch for 14.1.2.0.0 will apply to 12.2.1.4.0. Test patches in a non-production environment before production rollout to validate compatibility with custom extensions and dependent systems. Oracle typically provides patches through their Patch Cloud and My Oracle Support portal. Coordinate patching with change management processes and schedule maintenance windows with minimal business disruption. Verify patch application by confirming the patched version number and re-running vulnerability scans post-deployment.
Detection guidance
Monitor WebCenter Content HTTP access logs for privilege escalation attempts, particularly requests from low-privileged user accounts accessing administrative endpoints or APIs. Alert on unusual patterns: rapid API calls, access to sensitive system folders by non-administrative users, or changes to user role assignments initiated by accounts that should not have such permissions. Implement SIEM rules to flag any successful privilege changes. Review audit logs for creation or modification of system accounts outside of normal administrative procedures. Network-based detection should flag suspicious HTTP request patterns typical of privilege escalation probes. Test detection rules with authorized security teams before deploying to production monitoring.
Why prioritize this
Despite not yet appearing on CISA's KEV list, this vulnerability merits immediate prioritization due to its high CVSS score (8.8), ease of exploitation, and comprehensive impact (confidentiality, integrity, availability). The requirement for prior user credentials significantly limits spread but does not reduce severity—many organizations struggle with credential hygiene and segregation. WebCenter Content often stores business-critical documents and intellectual property, making compromise high-value for attackers. The affected versions are in active use in enterprises; older versions facing end-of-support may have longer remediation timelines, increasing risk accumulation. Organizations should treat this as equivalent to a zero-day until patches are validated in production.
Risk score, explained
The CVSS 3.1 score of 8.8 reflects the confluence of several factors: unrestricted network access (AV:N), low attack complexity (AC:L), and complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H). The requirement for low-level user privileges (PR:L) prevents the score from reaching critical (9.0+) but remains a substantial threat vector given common credential compromise scenarios. The lack of required user interaction (UI:N) means exploitation is deterministic once an attacker obtains valid credentials. No scope change (S:U) indicates the impact is confined to the vulnerable component, not adjacent systems—though in practice, compromised document repositories often serve as stepping stones for lateral movement.
Frequently asked questions
Do I need a patch immediately if our WebCenter Content instance is on an isolated network with IP-based access controls?
Isolation reduces but does not eliminate risk. If any trusted internal user, contractor, or service account could be compromised, the vulnerability remains exploitable. Prioritize patching within your standard maintenance cycle, but do not defer indefinitely. Implement additional monitoring for anomalous access patterns as an interim control.
What should I do if my organization is running an older version of WebCenter Content not mentioned in this advisory?
Consult Oracle's official advisory and your current support contract to determine if your version is affected. Older unsupported versions may have limited or no patches available; consider upgrading to a current supported version as part of long-term remediation. In the interim, apply network segmentation and credential-based access controls.
Will enabling multi-factor authentication prevent exploitation of this vulnerability?
MFA will not prevent exploitation of this vulnerability directly, since the attack requires HTTP protocol access and does not involve credential theft. MFA does reduce the risk that an attacker can initially obtain valid low-privileged credentials through phishing or password reuse. Use MFA as one layer in defense-in-depth, not as a substitute for patching.
How should I prioritize this against other Oracle security updates?
If your organization uses other Oracle products, review Oracle's published advisory for relative severity and business impact. This CVE-2026-35322 warrants high priority given its 8.8 CVSS score and ease of exploitation. Coordinate patching across your Oracle estate to minimize maintenance overhead, but do not delay WebCenter Content patches to wait for other updates if they have independent release schedules.
This analysis is provided for informational security purposes based on publicly available vulnerability data. Organizations must verify all remediation steps, patch versions, and compatibility against official Oracle advisories and in their own environments before production deployment. SEC.co does not provide warranty regarding patch availability, timing, or compatibility. Consult Oracle Support for definitive guidance. This document does not constitute legal advice or compliance guidance specific to your regulatory obligations. Conduct independent risk assessment aligned with your organization's policies and threat model. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-35262HIGHOracle Data Integrator Authentication Bypass – Data Exposure Risk
- CVE-2026-35269HIGHOracle Identity Manager REST WebServices Authentication Bypass
- CVE-2026-35271HIGHOracle PeopleSoft WebLogic Unauthenticated Data Access Vulnerability (CVSS 8.7)
- CVE-2026-35275HIGHOracle VM VirtualBox Shared Folders Privilege Escalation Vulnerability (CVSS 7.5)
- CVE-2026-35277HIGHOracle REST Data Services Authorization Bypass
- CVE-2026-35311HIGHOracle WebLogic Server Remote Takeover via Low-Privilege Access Control Flaw
- CVE-2026-35314HIGHOracle Access Manager Authentication Bypass (CVSS 7.3)
- CVE-2026-35315HIGHOracle WebCenter Content Remote Takeover via Low-Privilege HTTP Access