---
id: "GHSA-mgrx-3hqw-485h"
kind: "vulnerability"
aliases: ["GHSA-mgrx-3hqw-485h"]
title: "Duplicate Advisory: INVITED users auto-promoted via SSO email match (invite-token bypass)"
severity: "critical"
cvss: 7.7
epss: null
exploited: false
status: "withdrawn"
category: "package"
products: [{"name": "flowise", "fixed": [], "affected": "<= 3.1.4", "ecosystem": "npm"}]
ecosystems: ["npm"]
tags: ["cwe-287", "flowise", "npm", "package", "self-hosted", "sso"]
not_affected_if: ["single-user-mode", "sso-disabled"]
published_at: "2026-09-26T15:31:13+00:00"
first_seen_at: "2026-11-05T15:20:50+00:00"
updated_at: "2026-11-05T15:21:59+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-mgrx-3hqw-485h", "first_seen_at": "2026-11-05T15:20:50+00:00"}]
exploit_sources: []
---

# Duplicate Advisory: INVITED users auto-promoted via SSO email match (invite-token bypass)

Flowise through 3.1.4 with SSO enabled can auto-activate a user whose invitation is still pending when an SSO login arrives with that user's email address. An attacker who can authenticate at any configured SSO provider with the invitee's email gets the invited user's organization access without the emailed invitation token.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- npm:flowise affected <= 3.1.4 fixed no fixed version listed

## How to check

- Check the installed Flowise version (`npm ls flowise` or the image tag) against the range in the advisory.
- Confirm whether SSO is enabled in Enterprise or platform mode.
- Look for users in INVITED status in the Flowise database.

## Timeline

- 2026-11-05T15:20:50+00:00 ghsa https://github.com/advisories/GHSA-mgrx-3hqw-485h

## Documents

- [advisory] Maintainer's advisory: github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-vf3j-89vf-r697

## From the sources

### Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-vf3j-89vf-r697. This link is maintained to preserve external references.

### Original Description
Flowise through 3.1.4 (Enterprise/platform mode with SSO enabled) contains an authentication bypass in the SSO login path. When an SSO callback arrives with an email matching a user whose status is INVITED, verifyAndLogin (SSOBase.ts:80-94) copies the user record from the database — including the server-stored single-use invitation tempToken — into the data passed to AccountService.register(). The register handler's token lookup, email match, and expiry checks therefore pass trivially against the server's own token instead of a caller-supplied one, and the account and its organization membership are flipped to ACTIVE. As a result, anyone able to authenticate at any configured SSO provider using a pending invitee's email address as the email claim can take over that invitation and obtain the invited user's access to the organization without ever possessing the emailed invitation token, for as long as the invitation is valid (24 hours by default). At the time of the advisory no patched version was available.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_