Browse / AI Framework and Platform Flaws / Authentication and access control
Authentication and access control
256 records in AI Framework and Platform Flaws.
- 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: 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.
- MindsDB has an Improper Access Control Issue A missing access control in the BYOM handler's exec wrapper lets remote callers upload files to the server without restriction.
- 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.
- New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud An empty Stripe webhook secret makes signatures trivially computable, and orders from other gateways can be fulfilled, crediting unpaid quota.
- 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 TTS endpoint accepts arbitrary credential IDs — enables API credit abuse via stored credentials The TTS generate route skips authentication and accepts any credential ID in the body, letting callers spend stored provider API keys belonging to others.
- Flowise: Weak Default Express Session Secret A hardcoded fallback session secret lets anyone forge signed session cookies and impersonate other users.
- Flowise: Improper Mass Assignment in Account Registration Enables Unauthorized Organization Association The registration endpoint maps unfiltered client JSON onto internal models, letting attackers set organization, workspace and role fields during signup.
- 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.
- Flowise: Weak Default JWT Secrets Hardcoded fallback JWT secrets let anyone who knows the defaults forge tokens for any account.
- Flowise: resetPassword Authentication Bypass Vulnerability The account service's password reset logic can be reached without authentication, letting remote attackers change other users' passwords.
- Flowise: Weak Default Token Hash Secret A hardcoded fallback secret is used to encrypt identifiers in tokens, so anyone who knows the default can forge tokens.
- PraisonAI: Cross-Origin Agent Execution via Hardcoded Wildcard CORS and Missing Authentication on AGUI Endpoint The agent endpoint has no auth and sends a wildcard CORS header, so any website can run agents and read the responses.
- LiteLLM: Password hash exposure and pass-the-hash authentication bypass User endpoints return stored password hashes to any authenticated user, and login accepts that hash in place of the password, allowing account takeover.
- parisneo/lollms has an insufficient session expiration vulnerability Existing session tokens remain valid after a password reset and last about 31 days, so a stolen token keeps working.
- LoLLMs is vulnerable to Improper Access Control through weak secret key A guessable JWT signing key can be brute-forced offline, and the recovered key lets an attacker forge admin tokens to reach restricted endpoints.
- 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.
- LiteLLM: Authentication bypass via OIDC userinfo cache key collision The OIDC userinfo cache keys on the first 20 characters of the JWT, so a forged token sharing that prefix gets the cached identity of a legitimate user.
- mlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization Job submission and management endpoints accept requests without credentials when basic-auth is enabled, letting any network client create and cancel jobs.
- PraisonAI Has Missing Authentication in WebSocket Gateway The gateway accepts WebSocket connections and lists agents without authentication, letting any network client send messages to agents and their tools.
- 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 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'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.
- n8n Vulnerable to LDAP Filter Injection in LDAP Node Unescaped LDAP metacharacters in user input reach the search filter of the n8n LDAP node, letting attackers alter queries and bypass workflow checks.
- n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account Takeover LDAP login automatically links an identity to any local account with a matching email, so a user who controls their LDAP email can take over an admin account.
- 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.
- n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACK With an environment flag set, the OAuth callback skips verifying that the state belongs to the current user, so tokens are stored in an attacker-controlled credential.
- New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure The secure verification endpoint marks a passkey step-up as complete when the account merely has a passkey registered, without checking an actual assertion.
- 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.
- Unauthenticated remote shutdown in nltk.app.wordnet_app Any client that can reach the WordNet browser's port can stop the server with one unauthenticated GET request.
- Langflow is Missing Ownership Verification in API Key Deletion (IDOR) The API key delete route checks only that the caller is logged in, then deletes any key by ID without confirming ownership.
- Flowise Missing Authentication on NVIDIA NIM Endpoints The NVIDIA NIM route prefix is whitelisted past global auth, so unauthenticated callers reach token retrieval and container management endpoints.
- 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.
- Flowise has Authorization Bypass via Spoofed x-request-from Header The API middleware trusts a client-supplied internal header to skip API key checks, letting any authenticated tenant session reach administrative endpoints.
- n8n has Webhook Forgery on Zendesk Trigger Node Requests to a Zendesk trigger webhook URL are accepted without verifying the HMAC signature, so anyone knowing the URL can start the workflow with forged data.
- n8n has an Authentication Bypass in its Chat Trigger Node The Chat Trigger's n8n user authentication can be circumvented, letting unauthenticated requests reach the webhook workflow.
- n8n: Webhook Forgery on Github Webhook Trigger The GitHub trigger never checks HMAC signatures, so anyone who knows the webhook URL can send forged events that start the workflow.
- n8n has an SSO Enforcement Bypass in its Self-Service Settings API An SSO-authenticated user can disable SSO enforcement on their own account through a settings endpoint, then set a local password and log in directly.
- MLflow Use of Default Password Authentication Bypass Vulnerability Hard-coded default credentials in the MLflow basic auth file let remote callers authenticate and reach administrator-level access.