CVE-2025-58434

Read full 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.

CVSS 9.8 (CRITICAL)

Attention and evidence

HYPE SCORE

0.0/10

REALITY · THREAT PRIORITY

5.9/10

General review priority; not probability

Evidence confidence: PoC published; attacks unconfirmed

Why this priority?

Technical severity: CVSS 9.8: +3.43
Fresh EPSS: 82.58%: +2.06
Published PoC; attacks unconfirmed: +0.40

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Based on public data to date.

Hype components

Headline sample (25%)

0/100

Press, 30 days (60%)

0/100

Grounded branding (15%)

0/100

HYPE TOTAL0/100

Sources and documents

No source documents yet.

Score evolution

● Hype ● Reality

Earlier evidence-support scores are retained in history; this chart shows only the current priority definition.

First record: hype 0.0 · reality 5.9 (2026-11-02 15:14). The curve appears once the score changes.

Public exploit evidence

Public exploit entries / repo candidates

Source entries and unverified repository candidates are counted separately.

Public exploit evidence

exploitdb #52557 2026-05-13

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs.

Evidence in context

Confidence in exploitation evidence: PoC published; attacks unconfirmed
Priority basis: Exploitation in attacks unconfirmed; CVSS 9.8; EPSS 82.6%
Attention, last 30 days: 0 distinct story titles; 0 press documents; 0 publisher domains.
Technical potential: network access, no prior privileges, no user interaction.
Observed activity: Public PoC evidence is present.
Known scale: Not quantified.
Evidence confidence basis: Published PoC artifact; functionality unverified

Score evaluated: 2026-11-05 13:59:42.332197+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z

Source event timeline

Published

12 Sep 2025, 17:37

Score calculated

05 Nov 2026, 13:59

PoCs on GitHub

1 repositories