flowise-ui
Affected
- introduced
0, fixed3.0.10(semver)
Fixed versions
3.0.10
Fix
- Fixed version
3.0.10npm install [email protected]
Advisory
Also known as: CVE-2025-71328
Flowise does not Prevent Bypass of Password Confirmation - Unverified Password Change
Summary
Bypass of Password Confirmation - Unverified Password Change (authenticated change without current password)
An authenticated user is allowed to change their account password without supplying the current password or any additional verification. The application does not verify the actor’s authority to perform that credential change (no current-password check, no authorization enforcement). An attacker who is merely authenticated (or who can trick or coerce an authenticated session) can set a new password and gain control of the account. (ATO - Account Takeover)
Details
Occurence - code:
https://github.com/FlowiseAI/Flowise/blob/main/packages/ui/src/views/account/index.jsx#L278
Remote and physical scenarios can be considered.
PoC
Repro steps:
POC:
Password changed, and notice "Password updated" message.
Screenshot:
<img width="467" height="526" alt="secpw" src="https://github.com/user-attachments/assets/4cc52978-9f37-42ca-a2b2-7285c4da9f1c" />
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 email - part of credentials). (gain persistence)
High Basis: The source's own band: HIGH
0, fixed 3.0.10 (semver)3.0.10
3.0.10npm install [email protected]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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0