CVE-2025-58434
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlowise 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFlowise versions 3.0.5 and earlier have an authentication bypass in the forgot-password endpoint that returns a valid password reset tempToken directly in the API response without any verification. This allows unauthenticated attackers to generate reset tokens for any user and reset their password, achieving complete account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Flowise versionCheck the package.json file in the Flowise installation directory, or run 'npm list flowise' or check the Docker image tag if running in a containerAffected if Version is 3.0.5 or earlier (< 3.0.6)
-
Verify forgot-password endpoint is exposedLocate the Flowise API server and confirm the /api/v1/forgot-password endpoint is accessible (check server listen address, firewall rules, and reverse proxy configuration)Affected if The endpoint is reachable from untrusted networks without additional authentication layers
-
Inspect forgot-password response for token leakageSend a POST request to the forgot-password endpoint with a valid username/email and examine the JSON response body. Look for fields such as 'tempToken', 'resetToken', 'token', or similar that contain actual token valuesAffected if The API response contains a usable password reset token directly in the response body (not just a success message)
-
Check if email delivery is the only token transportReview Flowise configuration files (config/*, .env) or source code for the forgot-password implementation. Verify that tokens are sent exclusively via email and never included in API responsesAffected if Tokens can be obtained without email delivery (tokens appear in API response)
-
Confirm token validation configurationReview the password reset token implementation to verify single-use enforcement and short expiry times are enforced server-sideAffected if Tokens are not validated as single-use or have excessively long expiration windows
You are affected if your Flowise version is 3.0.5 or earlier AND the forgot-password API endpoint returns a reset token directly in the response rather than only delivering it via email.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.0.6
Upgrade to version 3.0.6 or later. Configure the forgot-password endpoint to not return tokens in responses, deliver tokens only via email, use generic success messages to prevent enumeration, and implement strict token validation (single-use, short expiry).
Flowise 3.0.6
- Upgrade Flowise to version 3.0.6 or later to obtain the patched code from commit 9e178d68873eb876073846433a596590d3d9c863
- Verify that the `forgot-password` endpoint now returns only a generic success message and does not expose the `tempToken` in the API response
- For self-hosted deployments: restart the Flowise service after upgrading to ensure the patched code is loaded
- For cloud deployments: confirm with Flowise that the service has been updated to version 3.0.6 or later
- Audit existing user accounts for any suspicious password reset activity that may have occurred before the patch was applied
- Monitor password reset endpoints going forward for any anomalous requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58434 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data