Advisory

GHSA-x39m-3393-3qp4

Also known as: CVE-2025-71337

Summary

Flowise doesn't Prevent Bypass of Password Confirmation through Unverified Email Change (credentials)

Details

Summary
Unverified Email Change - Email as part of Credential / Unverified Account Recovery Channel Change

The application allows changing the account email address (used as a login identifier and/or password recovery address) without verifying the requester’s authority to make that change (no confirmation to the old email, no authentication step). Because email often functions as a credential or recovery channel, unverified email changes enable attackers to take over accounts by switching the account’s recovery/login address.

Details
Occurence - code:
https://github.com/FlowiseAI/Flowise/blob/main/packages/ui/src/views/account/index.jsx#L211

Remote and physical scenarios can be considered.

PoC
Repro steps:

  1. As logged in user https://cloud.flowiseai.com/account scroll down to 'Profile' section
  2. Change email to the new email
  3. Notice Unverified Password Change (authenticated change without current password)

Later this email is needed as credentials to log in or reset password feature.

POC:
Email changed, and notice "Profile updated" message.

Screenshot
<img width="329" height="357" alt="secbug" src="https://github.com/user-attachments/assets/d3c77835-35bb-47dc-8cd2-83e4e266e5a4" />

Impact
Full account takeover (ATO) of affected accounts (loss of confidentiality and integrity of account data).
User account recovery mechanisms (password reset flows tied to email) can be bypassed or abused if combined with this issue and the second one which I've reported (similar security issue with the password - part of credentials). (gain persistence)

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-11-14 20:56 UTC
Modified
2026-07-08 07:10 UTC

Affected packages and fixes

flowise-ui

npm · All systems

Affected

  • introduced 0, fixed 3.0.10 (semver)

Fixed versions

3.0.10

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences