CVE-2024-7990
| CVE ID | CVE-2024-7990 |
| Vendor Disposition | Rejected, out of scope |
| Published | 2025-03-20 |
| Issuing CNA | huntr / Protect AI (from a bounty report) |
| Claimed Severity | High (CVSS 8.4, CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H) |
The issuing CNA has withdrawn the record, so the official CVE entry now carries the REJECTED state and NVD mirrors it. The public record now matches Open WebUI's vendor disposition below, confirming our assessment that this was not a genuine vulnerability. There is no advisory and no affected Open WebUI release.
Timeline
This CVE was withdrawn by its issuing CNA after the dispute was escalated to the CVE Program. Open WebUI's assessment below is the basis on which the record was rejected.
| Date | Event |
|---|---|
| 2025-03-20 | huntr / Protect AI publishes the CVE. |
| 2026-07-22 | Open WebUI publishes this disposition, rejecting the report as out of scope. |
| 2026-07-22 | Open WebUI contacts huntr / Protect AI directly to dispute the record. |
| 2026-08-03 | Open WebUI follows up with huntr / Protect AI. No response is received and the record is unchanged. |
| 2026-08-08 | With no response from huntr / Protect AI, Open WebUI escalates this record to the CVE Program Root. |
| 2026-08-12 | The CVE Program opens a formal dispute with huntr / Protect AI under CVE Program Rule 4.1 (Vulnerability Determination) and requests the CNA's response. |
| 2026-08-12 | huntr / Protect AI replies to the CVE Program and agrees to withdraw the record. |
| 2026-08-13 | Officially rejected The record is updated on cve.org. The CVE record is now officially REJECTED. |
| Still open | The huntr report page has not followed the withdrawal. The report is still shown as Valid with a green check and its status as "Awaiting fix", while the CVE field on the same page reads Rejected. |
| 2026-08-14 | With the report status unchanged, Open WebUI raises the matter with the CVE Program, asking that records withdrawn by the CNA no longer be presented as valid and awaiting a fix. CNA Rule 4.5.2.3 states that a CNA's published vulnerability information "MUST generally support and MUST NOT contradict information published by the CNA in corresponding CVE Records". |
The record is now in the REJECTED state on cve.org, and NVD mirrors that state. No action is required from users, and the CVE should not be treated as an Open WebUI vulnerability.
Disclosure Pathway
No report corresponding to this CVE was filed through the project's official reporting channel (GitHub Security Advisories) prior to publication.
What the CVE Claims
In Open WebUI v0.3.8, the description field submitted to POST /api/v1/models/add is claimed to be rendered in chat without sanitization, so a stored script payload would execute for any user who views it, including administrators. The record classifies this as CWE-79 (stored cross-site scripting) and scores it CVSS 8.4 (High).
Why This Is Not a Vulnerability
The Field Is Admin-Only
POST /api/v1/models/add and POST /api/v1/models/update require Depends(get_admin_user). A non-administrator cannot create or edit a model, and therefore cannot set the description field at all. The report's premise that "an attacker can inject" a payload is false: only an administrator can write this field. The record's own CVSS vector concedes this with PR:H (high privileges required). Administrator-authored content rendering inside the administrator's own single-trust-domain, admin-governed instance is administrator authority, not a cross-privilege scripting vulnerability.
CWE-79 Does Not Hold
Stored cross-site scripting requires input that an attacker can control reaching a page unescaped. Here the input is not attacker-controllable: only an administrator can write it.
Severity
Because the field is administrator-only, no CVSS score applies. The record's own PR:H already concedes that only an administrator can reach the field.
Applicable Security Policy Rules
- Rule 1: Expected behavior. Administrator-authored content crosses no security boundary.
- Rule 3: Reports must reflect an understanding of the affected components. The record describes an ordinary user injecting a script into a model's description, when only an administrator can write that field.
- Rule 6: Reports must reflect an understanding of the role-based, single-trust-domain architecture. Text an administrator writes into their own instance and that the instance's own users then see is the administrator exercising authority they already hold, not one user attacking another.
- Rule 8: Setting a model description is an administrator action, and administrator actions are out of scope.
Impact to Users
No action required. The model description field is writable only by administrators.