Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover

published 2025-09-12 last yr. modified 2026-09-30 last mo. also EUVD-2025-29069 , GHSA-wgpv-6j63-x5ph

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 82.6%; EPSS 82.6% chance of exploitation in 30 days, percentile 99.6%
public exploits: 2; Metasploit and Exploit-DB, plus a Nuclei check

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.

Patch / fix

fixed in 2 links 1

npm flowise 3.0.6
flowiseai flowise 3.0.6

github.com/FlowiseAI/Flowise@9e178d6 commit

Is CVE-2025-58434 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2025-09-12 First public exploit (Metasploit auxiliary/admin/http/flowise_auth_bypass_cve_2025_58434)
2025-09-12 Published

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: total
Assessed: last yr. (2025-09-12)

Exploit prediction

82.59% chance of exploitation in the next 30 days, higher than 99.6% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

Metasploit auxiliary/admin/http/flowise_auth_bypass_cve_2025_58434 Flowise Authentication Bypass metasploit auxiliary, normal rank, 2025-09-12
EDB-52557 Flowise < 3.0.5 - Missing Authentication for Critical Function webapps, 2026-05-13
Nuclei template Flowise <= 3.0.5 - Account Takeover nuclei detection template
github.com https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-wgpv-6j63-x5ph referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	flowise	<3.0.6	3.0.6

Affected products

FlowiseAI Flowise

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality

References

github.com /FlowiseAI/Flowise/commit/9e178d68873eb876073846433a596590d3d9c863
web, patch
github.com /FlowiseAI/Flowise/security/advisories/GHSA-wgpv-6j63-x5ph
web, exploit, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2025-58434
advisory
github.com /FlowiseAI/Flowise
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

json critical feed