Products / flowise
flowise
114 records.
- 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: Public chatflow endpoints return unsanitized flowData including plaintext API keys, passwords, and credential IDs The public chatflow GET endpoint returns stored flow data unfiltered, so credential references, plaintext keys and passwords reach anonymous callers.
- Flowise: Cypher Injection in GraphCypherQAChain User text flows into an LLM-generated Cypher query that runs unsanitised against Neo4j, letting an attacker run arbitrary graph queries.
- Flowise: SSRF Protection Bypass (TOCTOU & Default Insecure) DNS rebinding exploits the gap between a validation lookup and the connection lookup, and the default empty deny list lets requests reach localhost.
- Flowise: APIChain Prompt Injection SSRF in GET/POST API Chains Unauthenticated users can inject API documentation through the question, steering the chain's LLM-built requests to arbitrary internal or external URLs.
- Flowise Execute Flow function has an SSRF vulnerability The Execute Flow node's base URL is not checked by the deny-list validator, so the server issues requests to internal addresses.
- Flowise: Code Injection in CSVAgent leads to Authenticated RCE Unsanitised custom Pandas read code is interpolated into Python run by pyodide in the CSV agent, so a crafted chatflow executes OS commands.
- Flowise: Authenticated RCE Via MCP Adapters The MCP stdio configuration accepts any command and only filters some patterns, so an allowed runner like npx can be given code-execution flags.
- Flowise: Parameter Override Bypass Remote Command Execution A substring check meant for file inputs accepts the keyword anywhere in a request, letting unauthenticated users override protected config such as NODE_OPTIONS and run commands.
- Flowise: Remote code execution vulnerability in AirtableAgent.ts caused by lack of input verification when using `Pandas`. User questions are inserted unsanitised into the prompt, so a crafted prompt makes the model generate Python that the Pyodide runtime executes.
- Flowise: SSRF Protection Bypass via Direct node-fetch / axios Usage (Patch Enforcement Failure) Several tools call raw HTTP clients directly instead of the centralised SSRF wrapper, so requests to internal addresses still succeed.
- Flowise: Path Traversal in Vector Store basePath The basePath parameter for vector store saves is used directly in filesystem writes, so authenticated users can write outside the intended directory.
- Flowise: SSRF Protection Bypass via Unprotected Built-in HTTP Modules in Custom Function Sandbox Custom function code can load built-in http, https or net modules that bypass the SSRF deny list, reaching internal services such as cloud metadata endpoints.
- 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: Sensitive Data Leak in public-chatbotConfig An unauthenticated endpoint returns full chatflow configuration, including stored API keys and authorization headers, to anyone who knows a chatflow ID.
- 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: Unauthenticated Information Disclosure of OAuth Secrets (Cleartext) via GET Request An unauthenticated endpoint returns an organisation's SSO provider configuration, including client secrets in plain JSON, to any caller.
- 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.
- Flowise: File Upload Validation Bypass in createAttachment Adding a JavaScript MIME type to chatflow upload settings lets an attacker store a Node web shell that then runs on the server.
- Flowise: Password Reset Link Sent Over Unsecured HTTP Password reset emails contain plain HTTP links, so a network attacker on the path can capture the token and take over accounts.
- Flowise affected by Server-Side Request Forgery (SSRF) in HTTP Node Leading to Internal Network Access The HTTP node in Flowise sends server-side requests to user-supplied URLs with no default restriction on private, loopback or metadata addresses.
- 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 Arbitrary File Upload via MIME Spoofing The unauthenticated upload endpoint trusts the client-supplied Content-Type, so attackers can store active files such as scripts by spoofing an allowed type.
- Flowise Allows Mass Assignment in `/api/v1/leads` Endpoint Object.assign copies every field from the unauthenticated request body onto the Lead entity, letting callers set internal fields such as id and chatId.
- 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.
- Flowise Vulnerable to PII Disclosure on Unauthenticated Forgot Password Endpoint The forgot-password endpoint returns the full user record, including email and identifiers, to unauthenticated callers, which reveals whether accounts exist.
- Flowise has Insufficient Password Salt Rounds A default bcrypt cost of 5 makes stored password hashes cheap to brute-force if the database is leaked.
- Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register) Flowise's registration endpoint is open by default, so anyone can create an account and log in.
- Flowise Fails to Invalidate Existing Sessions After Password Changes Existing sessions remain valid after a password change, so an attacker holding a stolen session token keeps access.
- Flowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright Packages Authenticated users can set attacker-chosen browser binary paths and arguments in Puppeteer or Playwright tools, which run on the host outside the nodevm sandbox.
- Flowise is vulnerable to arbitrary file exposure through its ReadFileTool The agent's read_file tool passes a caller-supplied path straight to the file store, so an authenticated user can read any file on the host.
- Flowise is vulnerable to arbitrary file write through its WriteFileTool The agent's write-file tool accepts any destination path without restricting it to the working directory, letting an authenticated user write files anywhere on the server.
- FlowiseAI/Flosise has File Upload vulnerability The upload endpoint accepts any file type and content, letting an authenticated user plant a server script that can run commands.
- Flowise vulnerable to RCE via Dynamic function constructor injection The Custom MCP node passes the server config it receives into a dynamic function constructor, so attacker-supplied config runs JavaScript on the host.
- Flowise vulnerable to XSS Unsanitised chat input and external web content returned by a custom function are rendered as HTML, so embedded scripts run in other users' browsers.
- Flowise Stored XSS vulnerability through logs in chatbot Chat prompts containing unsanitised HTML are stored in logs and rendered for administrators, so embedded script runs in the admin's browser.
- Flowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panel Chat message content is rendered unsanitised in the admin message viewer, so injected script runs for the admin and can read localStorage.
- Flowise has Remote Code Execution vulnerability The CustomMCP node passes the mcpServerConfig string to the Function constructor, so a crafted configuration value runs arbitrary JavaScript with Node.js privileges.
- Flowise has unsandboxed remote code execution via Custom MCP The Custom MCP feature launches attacker-chosen commands through a load-method endpoint that lacks proper authentication and role checks.
- FlowiseAI Pre-Auth Arbitrary Code Execution A filter expression string is compiled into a JavaScript function and executed on the server, letting the filter run arbitrary operating system commands.
- Flowise has an Arbitrary File Read An unauthenticated request sets the chatId parameter to a traversal path, which is joined onto the storage root because only chatflowId is validated, letting the attacker read arbitrary local files.
- FlowiseAI/Flowise has Server-Side Request Forgery (SSRF) vulnerability The link-extraction endpoint fetches any caller-supplied URL without validation, so callers can make the server request internal hosts and parse the responses.
- Flowise has arbitrary file access due to missing chat flow id validation The chatflowId from the request body is joined into a storage path without validation, so traversal sequences read or write files outside the storage directory.
- Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover The unauthenticated forgot-password endpoint returns a valid reset token in its response, letting an attacker reset any account's password by email address.
- Flowise OS command remote code execution Custom MCP server configuration lets unauthenticated network users run arbitrary OS commands through the server spawn feature.
- FlowiseDB vulnerable to SQL Injection by authenticated users An authenticated user imports a crafted chatflow file whose ID contains traversal and SQL-breaking input, which the import routine concatenates into a raw SQL query.