GHSA-X39M-3393-3QP4

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

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)

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

GHSA-X39M-3393-3QP4 has a CVSS score of 8.3 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-X39M-3393-3QP4? GHSA-X39M-3393-3QP4 is a high-severity missing authentication for critical function vulnerability in flowise-ui (npm), affecting versions < 3.0.10. It is fixed in 3.0.10. A critical operation is accessible without requiring any authentication.
2. How severe is GHSA-X39M-3393-3QP4? GHSA-X39M-3393-3QP4 has a CVSS score of 8.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of flowise-ui are affected by GHSA-X39M-3393-3QP4? flowise-ui (npm) versions < 3.0.10 is affected.
4. Is there a fix for GHSA-X39M-3393-3QP4? Yes. GHSA-X39M-3393-3QP4 is fixed in 3.0.10. Upgrade to this version or later.
5. Is GHSA-X39M-3393-3QP4 exploitable, and should I be worried? Whether GHSA-X39M-3393-3QP4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-X39M-3393-3QP4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-X39M-3393-3QP4? Upgrade flowise-ui to 3.0.10 or later.