CVE-2025-58434
PoC ×2largeUnauthenticated Account Takeover via Password Reset Token Leak in Flowise
The forgot-password endpoint in Flowise 3.0.5 and earlier returns sensitive information, including a valid password reset tempToken, in an API response that requires no authentication or verification (CWE-306, missing authentication for a critical function). An unauthenticated attacker who submits a reset request for any known or guessed user can read the tempToken directly from the response and reset that user's password, achieving complete account takeover with no privileges or user interaction required. Both the hosted cloud service (cloud.flowiseai.com) and self-hosted or local Flowise deployments that expose the same API are affected. Flowise fixed the issue in version 3.0.6 via commit 9e178d68873eb876073846433a596590d3d9c863 by securing the password reset endpoints. A public proof-of-concept exists and the issue is not yet in CISA KEV, but EPSS assigns a 49.9% probability of exploitation within 30 days (99th percentile), so broad scanning and exploitation attempts are considered likely.
What to do: Upgrade self-hosted Flowise to version 3.0.6 or later, which includes fix commit 9e178d68873eb876073846433a596590d3d9c863 securing the password reset endpoints. Until patched, restrict and rate-limit access to the forgot-password and password-reset endpoints, stop returning reset tokens or account details in API responses, and monitor reset activity for anomalies. For the cloud service, confirm the provider-side fix applies and enable multi-factor verification on sensitive accounts.
| flowiseai flowise (self-hosted/local deployments) | 3.0.5 and earlier; fixed in 3.0.6 |
| flowiseai flowise cloud (cloud.flowiseai.com) | all versions prior to the password reset endpoint fix (commit 9e178d6 / 3.0.6) |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5 and earlier, the `forgot-password` endpoint in Flowise returns sensitive information including a valid password reset `tempToken` without authentication or verification. This enables any attacker to generate a reset token for arbitrary users and directly reset their password, leading to a complete account takeover (ATO). This vulnerability applies to both the cloud service (`cloud.flowiseai.com`) and self-hosted/local Flowise deployments that expose the same API. Commit 9e178d68873eb876073846433a596590d3d9c863 in version 3.0.6 secures password reset endpoints. Several recommended remediation steps are available. Do not return reset tokens or sensitive account details in API responses. Tokens must only be delivered securely via the registered email channel. Ensure `forgot-password` responds with a generic success message regardless of input, to avoid user enumeration. Require strong validation of the `tempToken` (e.g., single-use, short expiry, tied to request origin, validated against email delivery). Apply the same fixes to both cloud and self-hosted/local deployments. Log and monitor password reset requests for suspicious activity. Consider multi-factor verification for sensitive accounts.
- Vendors
- flowiseai
- Products
- flowise
- Weakness
- CWE-306
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H