Summary
Flowise versions before 3.1.4 contain authorization gaps in Enterprise endpoints that may allow an authenticated Enterprise user to operate on resources owned by other tenants. Depending on the affected endpoint, this could enable unauthorized workspace deletion, organization membership changes, cross-organization role modification, or access to stored SSO secrets.
Affected context
The issue occurs in Flowise Enterprise deployments where multi-tenant endpoints perform resource operations without consistently verifying that the requesting principal owns the target workspace or belongs to the relevant organization. Risk is increased when an authenticated Enterprise user can reach endpoints for workspace administration, invitations, role management, or stored identity-provider configuration.
Exploit preconditions
- Attack surface: Enterprise HTTP endpoints that manage tenant-scoped resources
- Required access: An authenticated Flowise Enterprise account
- Trigger point: Requests that address another workspace, organization, role, invitation, or SSO-related resource
- Why exploitation is possible: Some authorization paths may confirm authentication without enforcing resource ownership or tenant membership
Why this happens
The underlying bug is an incomplete authorization check in multi-tenant resource handling. Authentication establishes that a caller has an account, but affected endpoint logic may fail to compare the requested resource's tenant or owner identity with the caller's authorized scope. This maps to CWE-862, Missing Authorization, because sensitive operations can proceed without an effective permission decision for the specific resource.
Potential impact
- An attacker may delete workspaces belonging to other tenants
- An attacker could add themselves to another organization
- Cross-organization roles may be modified without appropriate authorization
- Stored SSO secrets could be exposed or abused
- Tenant isolation may be weakened, causing organizational disruption or privilege escalation
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every
tenant-scoped operation rather than relying on authentication or client-side
restrictions.
Common defensive patterns include:
- Deriving tenant and ownership scope from the authenticated server-side identity
- Enforcing centralized, deny-by-default authorization checks for every resource operation
- Validating organization membership and role permissions before invitations, deletions, or role changes
- Avoiding direct exposure of stored SSO secrets and applying secret minimization and rotation controls
- Applying least privilege to administrative identities and service integrations
- Using consistent authorization middleware across all Enterprise endpoints
How teams detect issues like this
Organizations can look for:
- Static analysis and code review rules that flag resource queries or mutations lacking ownership predicates
- Endpoint tests using users from separate organizations to verify tenant isolation
- Signals of cross-tenant workspace deletion, unexpected invitations, or role changes
- Access attempts involving resources outside the caller's organization
- Policy enforcement requiring server-side authorization decisions for every tenant-scoped API action
Automated application security testing and authorization-focused regression suites can help identify inconsistent checks.

