Products / flowise
flowise
114 records.
- Flowise allows arbitrary file write to RCE A user-supplied file name joined to a storage path lacks validation, allowing writes outside the directory; overwriting package.json gives code execution.
- Flowise Pre-auth Arbitrary File Upload A path-prefix whitelist lets unauthenticated requests reach the attachments upload route, allowing arbitrary files to be written to local storage.
- FlowiseAI Flowise arbitrary file upload vulnerability The attachments endpoint accepts arbitrary uploaded files without adequate type or content restrictions.
- Flowise OverrideConfig security vulnerability Callers can override flow configuration at runtime, including prompts and node settings, reaching sandboxed code execution, SSRF, and data exfiltration.
- Flowise and Flowise Chat Embed vulnerable to Stored Cross-site Scripting The chat embed does not sanitise stored input, so injected script runs in viewers' browsers when messages are displayed.
- Flowise Authentication Bypass vulnerability Unauthenticated remote requests reach administrator-level API endpoints because access checks are missing in this version.
- Flowise Unauthenticated Denial of Service (DoS) vulnerability An unauthenticated request to the upload file retrieval endpoint with crafted input crashes the whole Flowise instance.
- Flowise Cross-site Scripting in api/v1/chatflows/id An unknown chatflow ID is echoed unescaped into an HTML 404 page, so a crafted URL runs script in the victim's browser.
- Flowise Cors Misconfiguration in packages/server/src/index.ts Flowise sends a wildcard CORS header, letting any origin read responses, and chained path injection can expose arbitrary server files.
- Flowise Cross-site Scripting in /api/v1/chatflows-streaming/id An unknown chatflow ID is echoed unescaped into a text/html 404 page, letting a crafted URL inject script.
- Flowise Cross-site Scripting in /api/v1/public-chatflows/id The 404 page reflects the unvalidated chatflow ID as text/html, so injected script runs in users' sessions.
- Flowise Path Injection at /api/v1/openai-assistants-file The file endpoint uses an unsanitised fileName parameter, letting callers read arbitrary files on the server.
- Flowise Cross-site Scripting in/api/v1/credentials/id An unknown ID is reflected unescaped into a text/html 404 page, letting attacker-supplied script run in a victim's session.
- Flowise vulnerable to code injection via api/v1 A crafted script sent to the v1 API endpoint is executed by the Flowise server, giving a remote attacker code execution.