[GH-ISSUE #22315] Security: Stored XSS via HTML file serving #74300

New Issue

GiteaMirror · 2026-05-13T07:00:47-05:00

GiteaMirror commented

2026-05-13 07:00:47 -05:00

Originally created by @Vext-Labs on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22315

This issue was filed in error and has been withdrawn. We apologize for the noise.

Originally created by @Vext-Labs on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22315 This issue was filed in error and has been withdrawn. We apologize for the noise.

GiteaMirror closed this issue

2026-05-13 07:00:48 -05:00

GiteaMirror commented

2026-05-13 07:00:49 -05:00

@Classic298 commented on GitHub (Mar 6, 2026):

🤨
what do you mean 03-06 (today) + 90 days public disclosure?
posting an issue is public disclosure.

Next time using the Github security reporting mechanism we have: https://github.com/open-webui/open-webui/security

and read through the vulnerability reporting guidelines to ensure you are reporting a valid vulnerability. I am reading the admin has to do something malicious. Might fall into one of the exceptions.

@Classic298 commented on GitHub (Mar 6, 2026): 🤨 what do you mean 03-06 (today) + 90 days public disclosure? posting an issue is public disclosure. Next time using the Github security reporting mechanism we have: https://github.com/open-webui/open-webui/security and read through the vulnerability reporting guidelines to ensure you are reporting a valid vulnerability. I am reading the admin has to do something malicious. Might fall into one of the exceptions.

GiteaMirror commented

2026-05-13 07:00:50 -05:00

@Vext-Labs commented on GitHub (Mar 6, 2026):

@Classic298 — You're absolutely right, and we apologize. We should have used your private security reporting at https://github.com/open-webui/open-webui/security instead of filing a public issue. That was a failure in our disclosure process.

You're also correct that the disclosure timeline is contradictory — posting publicly on day 1 is not "responsible disclosure + 90 days." That boilerplate language should have been removed for public filings.

Regarding the finding itself: you raise a fair point that it requires admin action (uploading a malicious HTML file). We understand if this doesn't meet your vulnerability threshold given the trust model for admin users.

We'll use your security reporting process for any future findings. Apologies for the noise.

@Vext-Labs commented on GitHub (Mar 6, 2026): @Classic298 — You're absolutely right, and we apologize. We should have used your private security reporting at https://github.com/open-webui/open-webui/security instead of filing a public issue. That was a failure in our disclosure process. You're also correct that the disclosure timeline is contradictory — posting publicly on day 1 is not "responsible disclosure + 90 days." That boilerplate language should have been removed for public filings. Regarding the finding itself: you raise a fair point that it requires admin action (uploading a malicious HTML file). We understand if this doesn't meet your vulnerability threshold given the trust model for admin users. We'll use your security reporting process for any future findings. Apologies for the noise.

GiteaMirror commented

2026-05-13 07:00:51 -05:00

@YasharF commented on GitHub (Mar 6, 2026):

@Classic298 Feel free to report this to Github. The issues is actually created by some automated AI spam thing which has spammed many repos.

@YasharF commented on GitHub (Mar 6, 2026): @Classic298 Feel free to report this to Github. The issues is actually created by some automated AI spam thing which has spammed many repos.

GiteaMirror commented

2026-05-13 07:00:52 -05:00

@Vext-Labs commented on GitHub (Mar 6, 2026):

Withdrawing this report. We apologize for the noise — this should have been filed through proper security disclosure channels, not as a public issue. Closing.

@Vext-Labs commented on GitHub (Mar 6, 2026): Withdrawing this report. We apologize for the noise — this should have been filed through proper security disclosure channels, not as a public issue. Closing.

GiteaMirror commented

2026-05-13 07:00:53 -05:00

@Vext-Labs commented on GitHub (Mar 6, 2026):

We apologize for the noise — these were inadvertently auto-reported as public GitHub issues, which should have never happened. They should have gone through proper security disclosure channels instead. Thank you for your understanding.

@Vext-Labs commented on GitHub (Mar 6, 2026): We apologize for the noise — these were inadvertently auto-reported as public GitHub issues, which should have never happened. They should have gone through proper security disclosure channels instead. Thank you for your understanding.

GiteaMirror commented

2026-05-13 07:00:54 -05:00

@Classic298 commented on GitHub (Mar 6, 2026):

@YasharF thanks for letting me know we will take appropriate action

@Classic298 commented on GitHub (Mar 6, 2026): @YasharF thanks for letting me know we will take appropriate action

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#74300