Summary
Flowise contains missing authorization checks on document store mutation endpoints, allowing authenticated workspace members with view-level permissions to perform operations beyond their assigned access.
By sending direct requests to unprotected upsert or refresh routes, an attacker may ingest documents, alter vector database contents, consume embedding API credits, and change knowledge bases used by downstream chatflows.
Affected context
The issue affects Flowise deployments where workspace members can reach document store mutation routes without an effective authorization check. It becomes risky when users with view-level access can directly invoke upsert or refresh operations, particularly where document stores and vector databases support downstream chatflows.
Exploit preconditions
- Attack surface: HTTP document store mutation endpoints
- Required access: An authenticated workspace account, potentially with view-level permissions
- Trigger point: Direct requests to document store upsert or refresh routes
- Why exploitation is possible: Endpoint-level authorization does not adequately enforce the caller's workspace or document store permissions
Why this happens
The vulnerability results from missing or incomplete authorization enforcement on state-changing API endpoints. The application permits an authenticated workspace member to invoke document ingestion and refresh operations without verifying whether that identity has the required privileges.
This maps to CWE-862: Missing Authorization, in which an application authenticates a user but fails to enforce access-control decisions for a protected operation.
Potential impact
- An attacker may add or ingest unauthorized documents into a knowledge base
- Vector database contents may be modified or refreshed without approval
- Downstream chatflows could use altered or poisoned knowledge
- Embedding API credits and related infrastructure resources could be consumed
- Workspace data integrity and trust boundaries could be weakened
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every document store mutation endpoint rather than relying on client-side controls or navigation restrictions.
Common defensive patterns include:
- Applying server-side permission checks to upsert, refresh, and related state-changing operations
- Verifying workspace membership, document store ownership, and operation-specific privileges
- Using deny-by-default authorization for mutation routes
- Separating view, ingestion, refresh, and administrative permissions where appropriate
- Limiting service credentials and embedding-provider access according to least privilege
- Enforcing quotas, approval workflows, and audit logging for expensive or high-impact operations
How teams detect issues like this
Organizations can detect authorization gaps through:
- Static analysis and route reviews that identify mutation handlers without centralized authorization middleware
- Code review checks for direct database or vector-store operations performed before permission validation
- API security testing using accounts with progressively lower privilege levels
- Policy enforcement requiring explicit authorization decisions for all state-changing endpoints
- Monitoring for unusual document ingestion, refresh activity, credit consumption, or access across workspace boundaries
Automated security review tools may help identify routes whose authorization checks are absent, inconsistent, or bypassable.

