Amwhoi

**Name of the Vulnerable Software and Affected Versions** Flowise versions prior to 3.1.5 **Description** An authentication bypass exists in the SSO login path when Enterprise/platform mode with SSO is enabled. The issue occurs when an SSO callback is received with an email matching a user with an INVITED status. The `verifyAndLogin()` function in `SSOBase.ts` copies the user record, including the server-stored single-use `tempToken`, into the data sent to `AccountService.register()`. This causes the token lookup, email match, and expiry checks to pass using the server's own token rather than a token provided by the caller, resulting in the account and organization membership being set to ACTIVE. Consequently, an attacker who can authenticate via a configured SSO provider using a pending invitee's email address can take over the invitation and gain access to the organization without the invitation token, provided the invitation is still valid. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Flowise versions prior to 3.1.5 **Description** The software resolves Single Sign-On (SSO) and local-password users based only on the email address, failing to store provider or subject identifier bindings. This allows an attacker to authenticate as any existing user by claiming the target email address through any configured SSO provider or by using a local password, regardless of the victim's original registration method. Successful exploitation grants full account access, including chatflows, credentials, and API keys. **Recommendations** Update to version 3.1.5 or later.

**Name of the Vulnerable Software and Affected Versions** Flowise versions prior to 3.1.5 **Description** When the server operates in queue mode with the dashboard enabled and is not in cloud mode (`MODE=queue`, `ENABLE BULLMQ DASHBOARD=true`, and `!isCloud()`), the `/admin/queues` endpoint is protected only by the `verifyTokenForBullMQDashboard` middleware. This middleware validates the JSON Web Token (JWT) but fails to perform role, permission, or workspace/organization scoping checks. Additionally, because the mount is located outside the `/api/v1/*` path, the global API gate is not applied. Consequently, any authenticated user, regardless of their privilege level or tenant, can access the Bull-Board UI to view all queues and job payloads across the entire instance. This exposure includes chat inputs, `overrideConfig` (which may contain credentials and prompts), `chatflow.flowData` graph definitions with custom function source code, credential IDs, system prompts, `chatIds`, files, and the originating `orgId`/`workspaceId`. Furthermore, write actions such as retry, remove, promote, and clean are accessible across all tenants. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, consider disabling the BullMQ dashboard by setting `ENABLE BULLMQ DASHBOARD=false` to minimize the risk of exploitation.