Skip to content
Fencer Intel
medium 6.9

CVE-2024-7035 json

Cross-Site Request Forgery (CSRF) in open-webui/open-webui

published last yr. modified 3mo ago also GHSA-p5vx-9hj8-cf4h , PYSEC-2026-1739 , EUVD-2025-6943

cvss
6.9
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
8.7%
EPSS 8.7% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

In version v0.3.8 of open-webui/open-webui, sensitive actions such as deleting and resetting are performed using the GET method. This vulnerability allows an attacker to perform Cross-Site Request Forgery (CSRF) attacks, where an unaware user can unintentionally perform sensitive actions by simply visiting a malicious site or through top-level navigation. The affected endpoints include /rag/api/v1/reset, /rag/api/v1/reset/db, /api/v1/memories/reset, and /rag/api/v1/reset/uploads. This impacts both the availability and integrity of the application.

Patch / fix

  • pypi open-webui 0.3.16

Is CVE-2024-7035 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

8.67% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • huntr.com https://huntr.com/bounties/2ac81740-410b-467a-9244-75d82a6f9e11 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 6.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:L
OSV 3.0 6.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:L
GitHub 3.0 6.9 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:L

Affected packages

ecosystem package affected fixed in
pypi open-webui
<=0.3.8
<0.3.16
0.3.16

Affected products

  • open-webui open-webui/open-webui

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.