CVE-2024-7806
CSRF in Openwebui Open Webui ≤ 0.3.8
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-7806 is a high-severity CSRF (CWE-352) vulnerability in Openwebui Open Webui. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-7806 is a Cross-Site Request Forgery (CSRF) vulnerability, classified under CWE-352, affecting open-webui/open-webui versions up to and including 0.3.8. The issue stems from the application's use of authentication cookies with the SameSite attribute set to Lax, combined with the absence of CSRF tokens. This flaw enables remote code execution (RCE) when exploited, as demonstrated by its CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high severity with network accessibility, low attack complexity, no required privileges, and user interaction needed for high impacts across confidentiality, integrity, and availability.
An attacker can exploit this vulnerability without authentication by crafting a malicious HTML page. When a victim user—potentially a non-admin—visits the attacker's page (for example, via a phishing link or malicious website), the browser automatically sends a CSRF request using the victim's session cookies. This request modifies the Python code of an existing pipeline within the application, allowing the execution of arbitrary code under the victim's privileges.
For mitigation details, refer to the primary advisory on the Huntr bounty page at https://huntr.com/bounties/9350a68d-5f33-4b3d-988b-81e778160ab8, which reported the issue. Security practitioners should upgrade to a patched version beyond 0.3.8 if available and implement CSRF protections such as tokens or stricter SameSite cookie policies in similar applications.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6923
Vulnerability Data
A vulnerability in open-webui/open-webui versions <= 0.3.8 allows remote code execution by non-admin users via Cross-Site Request Forgery (CSRF). The application uses cookies with the SameSite attribute set to lax for authentication and lacks CSRF tokens. This allows an attacker…
more
to craft a malicious HTML that, when accessed by a victim, can modify the Python code of an existing pipeline and execute arbitrary code with the victim's privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.3.2V3.5.1V10.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.
Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.
Contextual intelligence about emerging CSRF toolkits can be translated into updated anti-CSRF token or same-site policy configurations across applications.