Summary
Open WebUI could allow a non-administrator with write access to one external knowledge base to delete a shared administrator-owned external connection. This could make other knowledge bases that depend on the connection unavailable because deletion was authorized for the knowledge base without separately checking administrator privileges or dependent resources.
Affected context
The issue occurs in Open WebUI deployments using external knowledge-base connections and affected versions from 0.10.0 through 0.11.1. It becomes risky when a user who can write to a knowledge base can invoke its deletion endpoint, while the associated external connection is shared with other knowledge bases and is removed without an administrator authorization check or dependency validation.
Exploit preconditions
- Attack surface: The knowledge-base deletion API endpoint
- Required access: An authenticated non-administrator account with write access to an external knowledge base
- Trigger point: Deletion of the knowledge base through the affected API operation
- Why exploitation is possible: Authorization is applied to the target knowledge base, but the subsequent deletion of its shared external connection is not protected by a separate administrator check or dependency check
Why this happens
The underlying bug is an authorization boundary failure involving a resource-management operation. The endpoint validated permission to delete a knowledge base but did not independently authorize deletion of the administrator-owned external connection associated with it, nor verify whether other knowledge bases still depended on that connection. This maps primarily to CWE-863, Incorrect Authorization, and relates to CWE-269, Improper Privilege Management.
Potential impact
- A non-administrator may delete shared external connection configuration
- Other knowledge bases using the connection may become unavailable
- Users may experience interruption of knowledge retrieval or related workflows
- Administrative configuration and service availability may be reduced
- Recovery efforts may require restoring or recreating shared connection settings
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every resource
boundary and protecting shared configuration from lower-privileged users.
Common defensive patterns include:
- Require an explicit administrator or resource-owner authorization before deleting shared external connections
- Separate permissions for deleting a knowledge base from permissions for deleting its backing connection
- Check for dependent knowledge bases before allowing removal of shared resources
- Prefer safe failure or protected retention when dependency ownership is ambiguous
- Apply least privilege to knowledge-base management roles
- Use transactionality, audit logging, and recoverable deletion workflows for shared configuration
- Reduce input and trust assumptions by deriving resource relationships server-side rather than accepting client assertions
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review checks for endpoints that delete multiple related resources
- Review of authorization checks at each resource boundary, especially when ownership differs between parent and dependent objects
- Tests covering non-administrator access to shared-resource deletion paths
- Dependency-aware policy enforcement that blocks deletion while active consumers remain
- Audit monitoring for external connection deletion initiated by non-administrative identities
- Automated security review tools that flag authorization checks performed only on an initial resource

