Summary
CVE-2026-61008 is a critical, easily exploitable vulnerability in Oracle WebCenter Sites (part of Oracle Fusion Middleware) that allows an unauthenticated attacker with network access via HTTP to compromise the application. Successful exploitation can result in unauthorized creation, deletion, or modification of data, as well as complete read access to all data accessible to WebCenter Sites, making this a high-priority patching target for internet-facing deployments.
Technical details
- Root cause: The published CVE record describes an "easily exploitable vulnerability" in the WebCenter Sites component of Oracle Fusion Middleware that can be triggered without authentication. Oracle’s advisory has not published low-level technical root-cause detail (e.g., specific vulnerable class/endpoint) in public sources at this time.
- Trigger conditions: No authentication, no privileges, and no user interaction are required (PR:N, UI:N) — the attacker only needs network access to the application over HTTP.
- Attack vector: Network (AV:N), Low attack complexity (AC:L), Scope Unchanged (S:U) — consistent with a remotely exploitable web application flaw reachable over standard HTTP paths.
- Impact: High confidentiality impact (C:H) and high integrity impact (I:H), with no availability impact (A:N). This means attackers can read and modify/delete data accessible to the application but cannot directly crash or deny service to it.
Affected software
- Oracle WebCenter Sites 12.2.1.4.0
- Oracle WebCenter Sites 14.1.2.0.0
Severity
- CVSS v3.1 Base Score: 9.1 (Critical)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Mitigation and recommended actions
- Immediate: Apply the Oracle Critical Patch Update (CPU) for August 2026, which addresses CVE-2026-61008 for the affected WebCenter Sites 12.2.1.4.0 and 14.1.2.0.0 releases. Organizations should upgrade/patch to the fixed version specified in Oracle’s August 2026 CPU as soon as possible given the network attack vector and lack of required privileges.
- If immediate patching is not possible:
- Restrict network exposure of WebCenter Sites management and content-serving interfaces to trusted internal networks or VPN only; do not expose administration paths directly to the internet.
- Place a web application firewall (WAF) in front of internet-facing WebCenter Sites instances to help detect and block anomalous unauthenticated requests while patch deployment is scheduled.
- Monitor WebCenter Sites access and application logs for unusual unauthenticated requests or unexpected data modification/deletion activity until patched.
- Prioritize patching for any WebCenter Sites instance directly reachable from the internet, given the combination of Critical severity, network vector, and no authentication requirement.

