Get a Demo

Let's Patch It!

Book a short call with one our specialists, we'll walk you through how Endor Patches work, and ask you a few questions about your environment (like your primary programming languages and repository management). We'll also send you an email right after you fill out the form, feel free to reply with any questions you have in advance!

CVE

GHSA-x39m-3393-3qp4

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

GHSA-x39m-3393-3qp4

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

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)

Package Versions Affected

Package Version
patch Availability
No items found.

Automatically patch vulnerabilities without upgrading

Fix Without Upgrading
Detect compatible fix
Apply safe remediation
Fix with a single pull request

CVSS Version

Severity
Base Score
CVSS Version
Score Vector
C
H
U
-
C
H
U
8.3
-
3.0
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
C
H
U
-

Related Resources

No items found.

References

https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x39m-3393-3qp4, https://github.com/FlowiseAI/Flowise/pull/5294, https://github.com/FlowiseAI/Flowise, https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.10

Severity

8.3

CVSS Score
0
10

Basic Information

Ecosystem
Base CVSS
8.3
EPSS Probability
0%
EPSS Percentile
0%
Introduced Version
0
Fix Available
3.0.10

Fix Critical Vulnerabilities Instantly

Secure your app without upgrading.
Fix Without Upgrading