Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-58434: CWE-306: Missing Authentication for Critical Function in FlowiseAI Flowise

0
Critical
VulnerabilityCVE-2025-58434cvecve-2025-58434cwe-306
Published: Fri Sep 12 2025 (09/12/2025, 17:37:08 UTC)
Source: CVE Database V5
Vendor/Project: FlowiseAI
Product: Flowise

Description

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.

AI-Powered Analysis

AILast updated: 09/21/2025, 00:40:33 UTC

Technical Analysis

CVE-2025-58434 is a critical vulnerability affecting FlowiseAI's Flowise product, versions 3.0.5 and earlier. Flowise is a drag-and-drop interface used to build customized large language model workflows. The vulnerability resides in the 'forgot-password' endpoint, which improperly exposes a valid password reset temporary token (tempToken) without requiring any authentication or verification. This flaw allows an unauthenticated attacker to generate a reset token for any user arbitrarily and reset their password, resulting in a complete account takeover (ATO). The issue affects both the cloud-hosted service (cloud.flowiseai.com) and self-hosted or local deployments that expose the same API. The root cause is a missing authentication check on a critical function (CWE-306). The vulnerability was addressed in version 3.0.6 by securing the password reset endpoints. Recommended remediation includes never returning reset tokens or sensitive account details in API responses, delivering tokens only via registered email channels, responding with generic success messages to prevent user enumeration, enforcing strong validation of reset tokens (e.g., single-use, short expiry, origin binding, and email verification), applying fixes consistently across cloud and self-hosted environments, logging and monitoring reset requests for suspicious activity, and considering multi-factor verification for sensitive accounts. The CVSS v3.1 score is 9.8 (critical), reflecting the vulnerability's ease of exploitation (no authentication or user interaction required), and its severe impact on confidentiality, integrity, and availability due to full account takeover potential.

Potential Impact

For European organizations using FlowiseAI's Flowise platform, this vulnerability poses a significant risk of unauthorized account takeovers, potentially leading to data breaches, unauthorized access to sensitive AI workflows, and disruption of AI-driven business processes. Since Flowise is used to customize large language model flows, attackers gaining control could manipulate AI outputs, exfiltrate proprietary data, or disrupt AI services. The impact extends to both cloud and on-premises deployments, increasing the attack surface. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, face heightened regulatory and reputational risks if exploited. The vulnerability's ability to bypass authentication and reset passwords without user interaction makes it highly dangerous, potentially enabling widespread compromise if exploited at scale. Additionally, compromised accounts could be leveraged to launch further attacks within the organization's network or supply chain.

Mitigation Recommendations

European organizations should immediately upgrade all Flowise deployments to version 3.0.6 or later, where the vulnerability is patched. For self-hosted instances, ensure that the password reset API endpoints are not exposed publicly or are protected behind strong network access controls. Implement strict monitoring and alerting on password reset requests to detect anomalous patterns indicative of exploitation attempts. Enforce multi-factor authentication (MFA) on all accounts, especially those with administrative or sensitive access, to mitigate the impact of potential account takeovers. Review and harden email delivery mechanisms to ensure reset tokens are only sent to verified email addresses and never exposed in API responses or logs. Conduct regular security audits and penetration tests focusing on authentication and password reset flows. Educate users about phishing risks related to password resets and encourage immediate reporting of suspicious reset emails. Finally, apply consistent security controls and patches across both cloud and self-hosted environments to avoid discrepancies that attackers could exploit.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-09-01T20:03:06.531Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68c45b66055763ea6cf4ba8d

Added to database: 9/12/2025, 5:41:58 PM

Last enriched: 9/21/2025, 12:40:33 AM

Last updated: 10/30/2025, 2:09:54 PM

Views: 123

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats