Summary
Flowise exposes an unprotected account registration API endpoint that allows unauthenticated attackers to create arbitrary user accounts.
By registering accounts without credentials, remote attackers can then authenticate normally and gain full API access, making deployments highly vulnerable when the endpoint is reachable over the network.
Affected context
This vulnerability arises in Flowise deployments where the /api/v1/account/register endpoint is reachable from untrusted networks and is not protected by authentication or access control checks. It typically affects instances that expose the registration API directly to the internet or internal users without additional safeguards such as prior verification, invitation workflows, or gateway-level restrictions.
Exploit preconditions
- Attack surface: HTTP(S) interface exposing
/api/v1/account/register - Required access: Network-level ability to send requests to the Flowise API; no prior authentication is required
- Trigger point: Submitting a crafted registration request to the unauthenticated endpoint
- Why exploitation is possible: The endpoint fails to enforce authentication or authorization checks before allowing account creation, enabling arbitrary user registration and subsequent legitimate authentication flows
Why this happens
The underlying issue is a missing enforcement of authentication and authorization on a sensitive account management operation, aligning with CWE-306: Missing Authentication for Critical Function. The registration endpoint performs a state-changing action—creating user accounts—without verifying the caller's identity or trust level. This insecure design pattern occurs when account lifecycle APIs (registration, password reset, role assignment) are exposed without appropriate access control, relying solely on client behavior or assumptions about network trust rather than explicit server-side checks.
Potential impact
- Remote attackers may create arbitrary user accounts on the system
- Attackers could authenticate using the created accounts and gain full API access
- Unauthorized access to application data and workflows can occur
- Abuse of API functionality, such as data extraction, modification, or automation of large-scale requests
- Increased attack surface for further privilege escalation or lateral movement within the environment
General mitigation guidance
Effective mitigation focuses on enforcing strict authentication and authorization around all critical account-related endpoints and minimizing unauthenticated functionality. Common defensive patterns include:
- Treating registration, login, and account management as privileged operations that require controlled workflows (e.g., invite-only, admin-mediated, or identity provider-backed flows)
- Implementing server-side authentication checks on all sensitive endpoints, backed by a centralized access-control layer
- Applying role-based access controls so that newly created accounts have minimal privileges by default
- Using network and application gateways to restrict exposure of administrative or registration APIs to trusted users or networks
- Auditing and hardening default configurations to ensure that no critical endpoints remain unintentionally unauthenticated
How teams detect issues like this
Detection typically involves analyzing API design and access control implementation rather than looking for exploit payloads. Practical strategies include:
- Static review of routing and controller code to verify that authentication middleware is consistently applied to account-related endpoints
- Automated tests or security policies that assert "no critical function without authentication," covering registration, password reset, profile changes, and role assignment
- API gateway or WAF rules that flag or block unauthenticated requests to known sensitive paths such as
/api/v1/account/* - Periodic security-focused code reviews and architecture assessments to identify endpoints that were added without access control integration
- Leveraging automated application security testing tools to crawl the API surface and report any state-changing operations accessible without authentication

