Bypasses / Authorisation check
Authorisation check
147 cases that got past this protection.
- FlowiseAI: DatasetRow create+update mass-assignment allows cross-workspace row takeover Copying the full request body onto a database entity lets a client set its own workspace ID and move rows into another tenant's workspace.
- FlowiseAI: Evaluation create+update mass-assignment allows cross-workspace evaluation takeover Object.assign copies a client-supplied workspaceId and id onto evaluations, letting an attacker move or access records belonging to other workspaces.
- FlowiseAI: Evaluator create+update mass-assignment allows cross-workspace evaluator takeover Object.assign copies a client-supplied workspaceId into evaluator rows, letting a request move records into another workspace.
- n8n Has a Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints OAuth reconnect endpoints check read permission instead of update, so read-only users can replace stored credential tokens with their own.
- 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 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'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.
- PraisonAI has unsafe tool resolution in `ToolExecutionMixin.execute_tool`: undeclared `__main__` callables execute When a tool name is undeclared, the agent falls back to module globals and __main__ and runs any matching callable, which the permission gate does not stop.
- 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'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'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 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'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.
- n8n has Public API Variables IDOR that Allows Cross-Project Secret Disclosure An API key scoped to variable listing passes an arbitrary project id, and the handler returns variables without checking project membership.
- n8n Vulnerable to Hijacking of Unauthenticated Chat Execution The chat WebSocket does not check authorisation, so an unauthenticated client who knows a waiting execution ID can attach to it and submit input.
- n8n's Credential Authorization Bypass in dynamic-node-parameters Allows Foreign API Key Replay A user with shared workflow access supplies a foreign credential ID to dynamic parameter endpoints, making the server send another user's API key to an attacker-chosen URL.
- LiteLLM: Authenticated command execution via MCP stdio test endpoints MCP stdio test endpoints spawn attacker-supplied commands and only require a valid key, not the admin role, so any user can run commands.
- Flowise: Mass Assignment in DocumentStore Create Endpoint Leads to Cross-Workspace Object Takeover (IDOR) The create endpoint accepts a client-supplied primary key and saves the whole body, so it overwrites existing document stores owned by other workspaces.
- Flowise: Unauthenticated OAuth 2.0 Access Token Disclosure via Public Chatflow in Flowise A public endpoint exposes OAuth credential identifiers from chatflow data, and an unauthenticated refresh endpoint then issues access tokens.
- MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint The MLflow AJAX endpoint for model artifacts skips the experiment permission check, so users without access can download artifacts directly.
- LiteLLM: Privilege escalation via unrestricted proxy configuration endpoint The config update route lacks an admin role check, so any logged-in user can change proxy settings, register code handlers and overwrite admin credentials.
- 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.
- Langflow: Authenticated Users Can Read, Modify, and Delete Any Flow via Missing Ownership Check Flow read, update and delete routes query by flow ID alone with no ownership filter, letting any authenticated user act on other users' flows.
- MLFlow allows Tracing + Assessments Access Trace and assessment endpoints skip permission checks when basic auth is enabled, so any authenticated user can read traces and create assessments.
- 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.
- n8n Has External Secrets Authorization Bypass in Credential Saving Saving a credential that references an external secret by name returns its plaintext value without the external-secret list permission being checked.
- n8n is Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition A member user resolves another user's credential by ID, and a permission check skips generic HTTP credential types, letting a workflow decrypt and use them.
- New API: IDOR in VideoProxy allows cross-user video content access via missing ownership check The video proxy looks up generated tasks by ID alone without checking ownership, so any authenticated user can fetch another user's video.
- langflow has Unauthenticated IDOR on Image Downloads The image download route omits the authentication and ownership checks used by other file routes, so anyone with a flow ID and filename can fetch images.
- Flowise has IDOR leading to Account Takeover and Enterprise Feature Bypass via SSO Configuration The login-method update endpoint trusts an organization ID from the request body without checking the caller belongs to that organization, so any user can overwrite its SSO settings.
- Khoj has an IDOR in Notion OAuth Flow that Enables Index Poisoning The Notion OAuth callback trusts an attacker-supplied state value as the target user ID, binding the attacker's integration to a victim's account.
- Lobe Chat has IDOR in Knowledge Base File Removal that Allows Cross User File Deletion A logged-in user can delete knowledge-base files owned by other users because the removal endpoint omits its ownership check.
- Chainlit contains an authorization bypass vulnerability A user-controlled key in Chainlit lets a logged-in user view or take ownership of other users' threads.
- n8n: Webhook Node IP Whitelist Bypass via Partial String Matching The n8n webhook IP whitelist used substring matching, so a client whose address merely contains a trusted entry is accepted.
- LiteLLM Has an Improper Authorization Vulnerability A viewer role receives an overly privileged API key, letting it call admin endpoints and promote itself to proxy admin.
- Letta (previously MemGPT) incorrect access control vulnerability The users endpoint of an agent memory server fails to enforce access control, exposing sensitive data to unauthorised callers.
- open-webui Insecure Direct Object Reference (IDOR) vulnerability The memory update endpoint checks only that a memory ID exists, not that it belongs to the caller, so users can rewrite others' stored memories.
- litellm vulnerable to improper access control in team management Team management endpoints skip authorisation checks, so any caller can view, change or delete teams and their members.
- MLflow allows low privilege users to delete any artifact Users with only edit permission on an experiment can send DELETE requests that remove artifacts, which the documented permissions do not allow.
- Gradio's Component Server does not properly consider` _is_server_fn` for functions The Component Server does not check the server-function flag on functions, so non-server functions can be invoked.