CVE-2025-58434
BaseFortify
Publication date: 2025-09-12
Last updated on: 2025-09-20
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flowiseai | flowise | to 3.0.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Flowise (version 3.0.5 and earlier) involves the 'forgot-password' endpoint returning sensitive information, specifically a valid password reset 'tempToken', without requiring authentication or verification. This allows an attacker to generate a reset token for any user and reset their password directly, leading to complete account takeover.
How can this vulnerability impact me? :
The vulnerability can lead to a complete account takeover (ATO) by attackers, allowing them to reset passwords of arbitrary users without authorization. This compromises user accounts, potentially exposing sensitive data and allowing unauthorized actions within the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be done by monitoring and logging password reset requests to the `forgot-password` endpoint for suspicious activity, such as unusually high numbers of reset attempts or reset tokens being generated without authentication. Specific commands are not provided in the context, but generally, inspecting API request logs or using network monitoring tools to track calls to the `forgot-password` endpoint can help identify exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: do not return reset tokens or sensitive account details in API responses; ensure the `forgot-password` endpoint responds with a generic success message regardless of input to prevent user enumeration; require strong validation of the `tempToken` such as making it single-use, short expiry, tied to request origin, and validated against email delivery; apply these fixes to both cloud and self-hosted deployments; log and monitor password reset requests for suspicious activity; and consider implementing multi-factor verification for sensitive accounts.