open-webui Open WebUI up to 0.6.34 cross site scripting

Summaryinfo

A vulnerability has been found in open-webui Open WebUI up to 0.6.34 and classified as problematic. This impacts an unknown function. Performing a manipulation results in cross site scripting. This vulnerability was named CVE-2025-64495. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in open-webui Open WebUI up to 0.6.34. It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. The summary by CVE is:

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. In versions 0.6.34 and below, the functionality that inserts custom prompts into the chat window is vulnerable to DOM XSS when 'Insert Prompt as Rich Text' is enabled, since the prompt body is assigned to the DOM sink .innerHtml without sanitisation. Any user with permissions to create prompts can abuse this to plant a payload that could be triggered by other users if they run the corresponding / command to insert the prompt. This issue is fixed in version 0.6.35.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-64495 since 11/05/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 0.6.35 eliminates this vulnerability. Applying the patch eb9c4c0e358c274aea35f21c2856c0a20051e5f1 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-38257). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• open-webui

Name

• Open WebUI

Version

• 0.6.0
• 0.6.1
• 0.6.2
• 0.6.3
• 0.6.4
• 0.6.5
• 0.6.6
• 0.6.7
• 0.6.8
• 0.6.9
• 0.6.10
• 0.6.11
• 0.6.12
• 0.6.13
• 0.6.14
• 0.6.15
• 0.6.16
• 0.6.17
• 0.6.18
• 0.6.19
• 0.6.20
• 0.6.21
• 0.6.22
• 0.6.23
• 0.6.24
• 0.6.25
• 0.6.26
• 0.6.27
• 0.6.28
• 0.6.29
• 0.6.30
• 0.6.31
• 0.6.32
• 0.6.33
• 0.6.34

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion