The vulnerability is a bypass of the WebSocket origin check in OpenClaw's gateway when operating in trusted-proxy authentication mode. The root cause is located in the resolveHandshakeBrowserSecurityContext function in src/gateway/server/ws-connection/message-handler.ts. The provided patch explicitly modifies the logic within this function. Previously, the condition to enforce an origin check was hasBrowserOriginHeader && !params.hasProxyHeaders. This meant that if a request was identified as coming from a browser (had an Origin header) but also contained proxy headers (like X-Forwarded-For), the origin check was skipped. An attacker could exploit this by crafting a malicious webpage that initiates a WebSocket connection to the vulnerable OpenClaw gateway through a trusted reverse proxy. The proxy adds the necessary headers, causing the gateway to trust the connection and bypass the crucial origin validation. This allows the malicious site to inherit the proxy's authenticated session, potentially gaining operator.admin privileges, leading to sensitive information disclosure and unauthorized actions. The fix removes the proxy header exemption (!params.hasProxyHeaders), ensuring that all browser-originated WebSocket connections are subject to origin validation, regardless of whether they pass through a proxy.