HIGH 8.8

CVE-2026-35315: Oracle WebCenter Content Remote Takeover via Low-Privilege HTTP Access

A critical vulnerability in Oracle WebCenter Content allows authenticated users with low-level network access to gain complete control over the content server. An attacker who already has valid credentials or can access the system via HTTP can exploit this flaw to read, modify, or delete data, and potentially disrupt service. The vulnerability affects two widely-deployed versions of the product: 12.2.1.4.0 and 14.1.2.0.0.

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-35315 is a privilege-escalation vulnerability in Oracle WebCenter Content's Content Server component. The flaw is classified under CWE-284 (Improper Access Control) and stems from insufficient validation or enforcement of access boundaries. With a CVSS 3.1 score of 8.8, the vulnerability requires low-level privileges and network access via HTTP, but no user interaction. Once exploited, an attacker achieves complete system compromise, affecting all three security pillars: confidentiality (reading sensitive content), integrity (modifying or injecting content), and availability (disrupting or disabling the service).

Business impact

WebCenter Content often serves as the central repository for enterprise documents, policies, and sensitive intellectual property. Compromise of this system exposes all stored content to unauthorized access and modification. An attacker could exfiltrate confidential business documents, tamper with critical records, or render the content repository unavailable, disrupting document workflows and compliance processes. For regulated industries, this creates immediate data breach and audit risks.

Affected systems

Oracle WebCenter Content versions 12.2.1.4.0 and 14.1.2.0.0 are confirmed vulnerable. These are relatively recent builds within their respective release families (12.2.x and 14.1.x). Organizations running earlier or later patch versions should verify their specific build number against Oracle's advisory to confirm exposure.

Exploitability

The vulnerability is rated 'easily exploitable' because it requires only low-level authentication (a standard user account) and network access—no sophisticated techniques, special conditions, or user interaction needed. Any user with valid credentials to the WebCenter Content system can potentially trigger the flaw. In environments where accounts are shared or credentials are leaked, this dramatically increases risk.

Remediation

Apply the security patches provided by Oracle for affected versions. Oracle typically releases patches through its regular quarterly Critical Patch Update (CPU) cycle. Users must download and apply the relevant patch for their specific version (12.2.1.4.0 or 14.1.2.0.0) and test in a staging environment before production deployment. If patches are unavailable, restrict network access to WebCenter Content using firewall rules or network segmentation to limit exposure to trusted hosts.

Patch guidance

Contact Oracle for the specific patch version applicable to your WebCenter Content release. Patch availability and timing should be confirmed through Oracle's security advisory portal. Before applying patches to production, validate in a test environment to ensure compatibility with custom extensions or integrations. Plan patching during a maintenance window to minimize disruption. Verify patch application by confirming the updated version string and re-testing the vulnerability condition.

Detection guidance

Monitor access logs for unusual authentication patterns, especially repeated login attempts from unexpected sources or privilege escalation activities. Check for POST/PUT requests to sensitive content management endpoints from low-privilege accounts. Deploy Web Application Firewalls (WAF) configured to detect tampering or access control bypass attempts against WebCenter Content. Network intrusion detection systems should be tuned to flag anomalous HTTP traffic to the Content Server. Consider implementing enhanced logging and alerting around content modifications and access to sensitive repositories.

Why prioritize this

This vulnerability scores 8.8 (HIGH severity) and should be treated as urgent. It requires only low-level credentials and network access, making it highly exploitable in most enterprise environments where WebCenter Content is deployed. The impact scope covers all three security properties (confidentiality, integrity, availability), and compromise results in full system takeover. Even though it is not yet listed on the CISA KEV catalog, the combination of ease of exploitation and business-critical role of the affected system demands rapid patching.

Risk score, explained

The CVSS 3.1 base score of 8.8 reflects: (1) network-based attack vector requiring no special positioning; (2) low complexity—no race conditions or special setup; (3) low privilege requirement—standard user credentials suffice; (4) no user interaction needed; and (5) complete compromise across all impact categories (confidentiality, integrity, availability). The score does not account for business context (centrality of content repository) or environmental factors (pervasiveness of WebCenter Content in enterprises), which may warrant even higher prioritization.

Frequently asked questions

Do we need to patch immediately if we're not on versions 12.2.1.4.0 or 14.1.2.0.0?

No, those two specific versions are confirmed vulnerable. However, verify your exact patch level (not just the major version) with Oracle to confirm you are outside the affected range. If you are on a different version, consult the vendor advisory to determine whether your build is covered.

Can we mitigate this without patching?

Patching is the definitive fix. As a temporary measure, restrict network access to WebCenter Content using firewall rules, VPNs, or network segmentation to limit exposure to trusted sources. Disable unused features and accounts. However, these mitigations do not eliminate the vulnerability—patching is essential.

What should we look for in our logs to detect if this has been exploited?

Review access logs for unusual activity by low-privilege accounts accessing sensitive endpoints, unexpected content modifications, or rapid sequences of authenticated requests. Check for failed and successful logins from unusual IP addresses. A spike in HTTP 403 errors followed by 200 responses may indicate probing. Correlation with user behavior baselines is key.

Is this vulnerability in the CISA KEV catalog?

As of the current data, this vulnerability is not yet on the CISA Known Exploited Vulnerabilities list. However, its high CVSS score and ease of exploitation mean it could be added as threat actors develop exploits. Do not delay patching based on KEV status alone.

This analysis is based on official vulnerability data as of the stated publication date. CVSS scores and attack vectors are provided by the vendor and CVSS scoring bodies; SEC.co does not calculate or modify these scores. Specific patch version numbers and availability should be verified directly with Oracle's security advisory and release notes. Remediation timelines, compatibility notes, and organizational risk assessment must be evaluated in context of each organization's specific environment, business continuity needs, and patch management policies. This content is for informational purposes and does not constitute professional security advice or a guarantee of protection. Organizations should engage qualified security professionals to assess and remediate vulnerabilities in their specific deployments. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).