Products / open-webui
open-webui
165 records.
- Open WebUI: Cross-User File Access via Unchecked file_id in Folder Knowledge and Knowledge-Base Attach Endpoints Attach endpoints accept any file identifier without checking ownership, so an authenticated user can pull other users' files into their own retrieval context.
- Open WebUI: Missing permission check in files API allows authenticated users to list, access and delete every uploaded file File routes check only that a user is logged in and never filter by owner, so any account can list, read and delete other users' uploads.
- Open WebUI has a SSRF Bypass via HTTP Redirect Following in Web-Fetch and Image-Load Endpoints (not addressed by CVE-2025-65958) Redirects from allowed public URLs are followed without rechecking the target, reaching internal addresses through fetch and image-load paths.
- Open WebUI: Mass Assignment via FeedbackForm extra=allow Allows Feedback User ID Spoofing and Evaluation Data Manipulation Extra fields in feedback requests override the server-derived user ID, so records are attributed to other users.
- Open WebUI: Authenticated users can bypass model access control via exposed query parameter [AI-ASSISTED] An internal flag is bound from the URL query string, letting any logged-in user skip model access checks and call restricted models.
- Open WebUI has an IDOR vulnerability in the update_message_by_id API endpoint Group and DM channels only check membership when updating a message, so any member can edit messages written by other members.
- Open WebUI has an Indirect Object Reference (IDOR) in user notes The notes API does not check ownership, so any logged-in user can read other users' notes by ID.
- Open WebUI has Stored XSS in Banner Component via Improper Sanitization Order Banner content is sanitised before Markdown conversion, so a link produced afterwards carries a javascript: URL that is rendered unescaped.
- Open WebUI: Missing `workspace.tools` Authorization Check on Tool Update Endpoint Allows Privilege Escalation to Code Execution The tool update endpoint skips the workspace permission check that tool creation enforces, so a restricted user can replace a tool's Python code and run it.
- Open WebUI Has Stored Cross-Site Scripting in SVG Renderer Injected HTML or JavaScript placed in generated SVG code is saved and rendered in the application's origin, so the script runs for any viewer.
- Open WebUI has a CORS misconfiguration and session validation issue Permissive cross-origin rules and weak session validation let a malicious page take a logged-in admin's session and reach remote code execution with one click.
- Open WebUI has inconsistent authorization controls within memories API Memory endpoints do not consistently enforce ownership, letting any user query, view, delete and restore memories that belong to other users.
- Open WebUI Arbitrary File Write, Delete via Path Traversal Uploaded filenames containing dot-segments are not sanitised, so attackers can write files to arbitrary locations and then have them deleted.
- Open WebUI's Improper Authorization in Standard Channels Allows Message Updates with Read Permission Message update in standard channels checks only read permission, so any user with read access can edit messages written by other users.
- Open WebUI's Insecure Message Access Breaks Authorization Channel message update and delete endpoints check channel access but not message ownership, letting users change other users' messages by calling the API directly.
- Open WebUI has an LDAP Empty Password Authentication Bypass An LDAP login with an empty password succeeds on servers that accept unauthenticated simple bind, issuing a session for the target user.
- Open WebUI: Redis Cache Keys tool_servers and terminal_servers Missing Instance Prefix Enable Cross-Instance Cache Poisoning Redis keys for tool and terminal server configuration lack an instance prefix, so separate deployments sharing Redis overwrite each other's config.
- Open WebUI: Stale Admin Role in Socket.IO Session Pool Enables Post-Demotion Cross-User Note Access Socket.IO sessions keep the admin role captured at connect time, so a demoted user can still join and save restricted collaborative documents.
- Open WebUI has Improper Authorization Control Users pending approval can call the API directly because the role check exists only in the client interface, not on the server.
- Open WebUI vulnerable to Global Knowledge Base Enumeration via knowledge-bases Meta-Collection The collection access check only covers certain name prefixes, so querying the system knowledge-base collection lists every knowledge base's metadata.
- Open WebUI has Knowledge Base Destruction and RAG Poisoning via Unauthorized Collection Overwrite A web-retrieval endpoint accepts any collection name and overwrites it without ownership checks, so other users' vector collections can be deleted or poisoned.
- Open WebUI's Channel Access Grants Bypass filter_allowed_access_grants Channel create and update endpoints store access grants without the permission filter other resources apply, so users can set public wildcard grants.
- Open WebUI Vulnerable to Arbitrary File Upload and Path Traversal Uploaded attachment filenames with dot-segments are not sanitised, letting an uploader write files to arbitrary locations on the server.
- Open WebUI's Base Model Routing Bypasses Access Control via Model Chaining Composed models can point base_model_id at a restricted model, and the chained base model's access is never checked at request time or creation.
- Open WebUI Missing Access Check on Channel Members Endpoint for Standard Channels The channel member listing skips the access check for standard channels, letting any logged-in user enumerate members of a private channel given its ID.
- Open WebUI has Stored XSS in Pending User Overlay via Incorrect DOMPurify Application Order Running the sanitiser before Markdown parsing lets javascript: links created during parsing reach the page unfiltered, enabling stored script execution.
- open-webui Vulnerable to Stored XSS via Model Description A javascript: link in a model description survives sanitisation, becomes an anchor only after sanitising, and then runs when other users view the model.
- Open WebUI has Unauthorized File and Knowledge Base Content Access via RAG Vector Search Some retrieval paths query vector collections named by user input without the access check used elsewhere, so users can read files and knowledge bases they cannot access.
- Open WebUI: Deactivated Channel Members Retain Full Access to Group/DM Channels The channel membership check does not look at the active flag, so users removed from a group or DM channel can still read and post via direct API calls.
- Open WebUI's responses passthrough endpoint lacks access control authorization The responses proxy only checks that a user is logged in, not per-model access rules, so any authenticated user can call models that were restricted to others.
- Open WebUI's Mass Assignment via Pydantic extra='allow' Allows Creating Folders in Other Users' Accounts Folder creation copies client-supplied fields over the server-assigned owner, letting a user set another account as the folder owner.
- Open WebUI has stored XSS in Excel file preview A crafted spreadsheet's HTML preview is inserted into the page without sanitising, so embedded script runs when the user opens the preview.
- Open WebUI's Model Import Overwrites Any Model Without Ownership Check The model import route overwrites existing models by ID without any ownership or access grant check, so a permitted user can replace models they do not own.
- Open WebUI's Ollama Model Access Control Bypass via /api/generate, /api/embed, /api/embeddings, and /api/show Ollama proxy routes forward any model name after only a login check, skipping the model access grant enforced on the chat route.
- Read-Only Open WebUI Users Can Modify Collaborative Documents via Socket.IO The Socket.IO update handler checks only room membership, not write permission, so read-only collaborators can change the live shared document.
- Open WebUI has Broken Access Control in Tool Valves A regular member reads tool valve configuration, including third-party API keys, through an endpoint that does not restrict read access to admin-only values.
- Open WebUI has unauthorized deletion of knowledge files The knowledge file removal endpoint checks write access to the knowledge base but not that the file belongs to it, so files can be deleted from other knowledge bases.
- Open WebUI's process_files_batch() endpoint missing ownership check, allows unauthorized file overwrite A batch file-processing route checks only that the caller is logged in, letting any user overwrite stored file contents by UUID.
- Open WebUI vulnerable to Path Traversal in `POST /api/v1/audio/transcriptions` A crafted multipart filename makes the extension include slashes, so the write fails and the error response leaks the server's absolute data directory path.
- Open WebUI's Insecure Direct Object Reference (IDOR) allows access to other users' memories Any logged-in user can query other users' collection names, including memory collections, through the retrieval endpoint because ownership is never checked.
- Open WebUI vulnerable to Server-Side Request Forgery (SSRF) via Arbitrary URL Processing in /api/v1/retrieval/process/web An authenticated user can make the retrieval web-processing endpoint fetch any URL because the submitted address is not validated.
- open-webui is Vulnerable to Incorrect Access Control The task-stop endpoint cancels any LLM task by ID without checking that the requesting user owns it.
- Open WebUI Vulnerable to Stored DOM XSS via Note 'Download PDF' SVG markup in imported Markdown is inserted into the PDF export via innerHTML without sanitising, so script runs in the exporting user's session.
- Open WebUI Affected by an External Model Server (Direct Connections) Code Injection via SSE Events A malicious external model server sends SSE execute events that the frontend runs as JavaScript, so server-supplied content executes in users' browsers.
- Open WebUI vulnerable to Stored DOM XSS via prompts when 'Insert Prompt as Rich Text' is enabled resulting in ATO/RCE Prompt bodies inserted as rich text are converted to HTML and assigned to innerHTML without sanitisation, so stored markup runs in other users' browsers.
- Open WebUI Vulnerable to a Session Fixation Attack Markdown images in chat content make an admin's browser request an attacker URL, and session cookies lacking Secure and SameSite protections are sent with it.
- Open WebUI Unauthenticated Multipart Boundary Denial of Service (DoS) Vulnerability Appending characters to a multipart boundary forces unauthenticated upload parsers to scan each byte, exhausting CPU and memory on several endpoints.
- Open WebUI denial of service through endpoint for converting markdown An unauthenticated markdown-to-HTML endpoint can be sent payloads that take excessive time to convert, tying up the server.
- Open WebUI Unauthenticated Multipart Boundary Denial of Service (DoS) Vulnerability in api/chat/file A malformed multipart boundary with many trailing characters makes the upload handler process each character endlessly, hanging the server for all users.
- Open WebUI Cross-Site Request Forgery (CSRF) Vulnerability Missing CSRF protection on a cookie-authenticated route lets a malicious page edit pipeline Python code, which then runs with the victim's privileges.