OpenClaw Cross-Site Request Forgery Vulnerability

OpenClaw before version 2026.3.31 is susceptible to Cross-Site Request Forgery (CSRF) attacks. The vulnerability lies in the lack of browser-origin validation within the HTTP operator endpoints when the application operates in trusted-proxy mode. This allows an attacker to craft malicious HTTP requests originating from a user’s browser to perform unauthorized actions within the OpenClaw application. Successful exploitation of this vulnerability enables attackers to execute privileged operations, potentially leading to data modification or unauthorized access to sensitive functionalities. This vulnerability requires the application to be deployed in trusted-proxy mode to be exploitable.

Attack Chain

1. An attacker crafts a malicious HTML page containing a forged HTTP request targeting a vulnerable OpenClaw HTTP operator endpoint.
2. The attacker hosts the malicious HTML page on a website or delivers it through phishing.
3. A victim user, authenticated to the OpenClaw application, visits the malicious HTML page in their browser.
4. The victim’s browser automatically sends the forged HTTP request to the vulnerable OpenClaw endpoint.
5. Because the OpenClaw application lacks proper browser-origin validation, it processes the forged request.
6. The attacker is able to perform unauthorized actions as the authenticated user.
7. The attacker can modify user configurations or exfiltrate data.

Impact

Successful exploitation of this CSRF vulnerability in OpenClaw can lead to unauthorized modification of application settings, data manipulation, or even complete account takeover. While specific victim numbers are unavailable, the impact extends to any organization utilizing OpenClaw in a trusted-proxy deployment scenario. The vulnerability can potentially compromise data integrity and confidentiality, leading to significant operational disruptions.

Recommendation

• Upgrade OpenClaw to version 2026.3.31 or later to patch CVE-2026-41347.
• Deploy the Sigma rule below to detect suspicious HTTP requests lacking proper origin validation within your web server logs.
• Implement proper CSRF protection mechanisms, such as synchronizer tokens, in OpenClaw’s HTTP operator endpoints.