Skip to main content
CVE-2024-7043VulnerabilityPublished Updated

CVE-2024-7043: open-webui/open-webui · Missing Authorization

Affects open-webui/open-webuiSource CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubopen-webui/open-webuipkg:github/open-webui/open-webuiOther threatsAffected
  • =0.3.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the affected API endpoints to trusted administrators only, using network-level controls such as IP whitelisting or VPNs. 2. Implement robust authorization checks within the application to verify that only users with appropriate administrative privileges can list, view, or delete files. 3. Monitor API usage logs for unusual patterns, such as bulk file enumeration or deletion attempts, and set up alerts for suspicious activities. 4. If possible, disable the vulnerable endpoints temporarily until a patch or update is available. 5. Conduct a thorough audit of files accessed or deleted recently to identify potential data breaches or tampering. 6. Educate developers and administrators on secure API design and the importance of enforcing access controls. 7. Follow up with the open-webui project for official patches or updates and apply them promptly once released. 8. Consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized API calls targeting these endpoints.

Description

An improper access control vulnerability in open-webui/open-webui v0.3.8 allows attackers to view and delete any files. The application does not verify whether the attacker is an administrator, allowing the attacker to directly call the GET /api/v1/files/ interface to retrieve information on all files uploaded by users, which includes the ID values. The attacker can then use the GET /api/v1/files/{file_id} interface to obtain information on any file and the DELETE /api/v1/files/{file_id} interface to delete any file.

References

Community reviews

Loading reviews…