/

CVE-2026-21962

Severity:

CRITICAL RISK

(10.0)

Improper Access Control in Oracle WebLogic Server Proxy

CVE-2026-21962

Modified

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Data Access and Modification

Severity:

CRITICAL RISK

(10.0)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical improper access control vulnerability in the Oracle WebLogic Server Proxy Plug-in for Apache HTTP Server and IIS allows unauthenticated attackers over HTTP to gain unauthorized access to and manipulate data exposed through the Oracle HTTP Server and proxy plug-in.

When reachable over the network, a remote attacker can create, delete, or modify critical data, and read all data accessible via the affected Oracle HTTP Server and WebLogic proxy plug-in, with no prior authentication.

Affected context

This vulnerability affects Oracle Fusion Middleware deployments using the Oracle HTTP Server with the WebLogic Server Proxy Plug-in for Apache HTTP Server or IIS.

Impacted environments typically:

  • Expose Oracle HTTP Server endpoints over HTTP(S) to internal or external networks
  • Use the WebLogic Server Proxy Plug-in to front-end WebLogic-based applications
  • Rely on the proxy tier to enforce access control, isolation, or routing rules

The issue manifests where the proxy plug-in participates in request handling or routing decisions that should restrict or mediate access to backend resources.

Exploit preconditions

  • Attack surface: Network-accessible Oracle HTTP Server / WebLogic Server Proxy Plug-in endpoints over HTTP or HTTPS
  • Required access: None; the attacker can be completely unauthenticated
  • Trigger point: Sending crafted HTTP requests through the affected proxy plug-in to Oracle HTTP Server / WebLogic backend paths
  • Why exploitation is possible: The proxy plug-in performs inadequate access control or authorization checks, enabling requests to reach sensitive resources or perform unauthorized operations that should be restricted

Why this happens

The core issue aligns with CWE-284: Improper Access Control, where the component fails to correctly enforce restrictions on what operations a client can perform.

At an abstract level, the proxy plug-in treats incoming HTTP traffic as more trusted than it should, either:

  • Not applying required authorization checks, or
  • Misclassifying the privilege level of requests, or
  • Incorrectly mapping HTTP routes and methods to protected backend operations.

This broken enforcement boundary allows unauthenticated clients to reach data or functionality that should only be available to authenticated or higher-privilege users, resulting in both read and write access to critical data.

Potential impact

  • Unauthorized reading of sensitive or business-critical data exposed through Oracle HTTP Server / WebLogic-backed applications
  • Unauthorized creation of new data records in backend applications
  • Unauthorized modification of existing data, including critical configuration or business state
  • Unauthorized deletion of important data, potentially impacting integrity or auditability
  • Access escalation from a public or semi-trusted network zone into backend application surfaces that were assumed to be protected by the proxy layer

General mitigation guidance

Effective mitigation generally focuses on tightening access control at multiple layers and reducing implicit trust in intermediary components:

  • Enforce strict authentication and authorization at the application and WebLogic layers, assuming the proxy plug-in may not reliably enforce all controls.
  • Use explicit allowlists for exposed paths, methods, and backend resources; deny-by-default for routes not explicitly needed.
  • Segment network access so that only trusted networks or gateways can reach the Oracle HTTP Server and proxy plug-in where feasible.
  • Apply principle of least privilege to any backend resources reachable via the proxy, including limiting what operations can be performed by anonymous or low-privilege contexts.
  • Centralize access control policies and configuration, avoiding ad-hoc exceptions in proxy routing rules that might bypass checks.
  • Regularly review proxy and virtual host configurations to ensure that administrative or highly sensitive endpoints are not exposed through generic frontends.

How teams detect issues like this

Organizations can approach detection using layered review and monitoring techniques:

  • Static configuration review: Examine Oracle HTTP Server, Apache/IIS, and WebLogic proxy plug-in configurations for routes that expose sensitive operations without authentication or with overly permissive rules.
  • Access control audits: Map endpoints to required roles and compare against actual proxy and backend configurations to identify mismatches or unprotected paths.
  • Web and application logs: Monitor for suspicious unauthenticated requests performing state-changing operations (e.g., POST/PUT/DELETE) or accessing high-value endpoints.
  • Automated scanning: Use web application scanners and policy-as-code checks to detect anonymous access to endpoints that should require authentication.
  • Security testing in CI/CD: Incorporate automated checks that validate access control rules and attempt to exercise privileged endpoints as an unauthenticated client during pre-deployment testing.

Sources

SourceLink
oracle.comoracle.com/security-alerts/cpujan2026.html
github.comgithub.com/Ashwesker/Ashwesker-CVE-2026-21962/issues/1
web.archive.orgweb.archive.org/web/20260129165916/https://github.com/Ashwesker/Ashwesker-CVE-2026-21962/issues/1
x.comx.com/0xacb/status/2015473216844620280

Frequently asked

questions

Yes, if the affected Oracle HTTP Server / WebLogic proxy endpoints are exposed to the internet or any untrusted network, an unauthenticated remote attacker can attempt exploitation using HTTP requests.

No. The vulnerability is exploitable by unauthenticated users with simple network access over HTTP(S) to the affected proxy endpoints; no prior login or session is required.

Strengthen access control so that sensitive operations and data are protected at the backend application and WebLogic layers, not solely by the proxy. Apply deny-by-default routing, minimize exposed endpoints, and ensure that any critical functions enforce authentication and authorization even if reached through trusted intermediaries.

Adopt a defense-in-depth approach to authorization: treat front-end proxies as convenience layers rather than sole enforcement points, codify access control policies, regularly test them with automated and manual security tests, and review changes to proxy and server configurations under security-aware change management.

Find out what's already
exploitable in your codebase.