GHSA-FJH6-8679-9PCH

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:

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

POC:
Password changed, and notice "Password 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 email - part of credentials). (gain persistence)

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

GHSA-FJH6-8679-9PCH 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-FJH6-8679-9PCH? GHSA-FJH6-8679-9PCH 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-FJH6-8679-9PCH? GHSA-FJH6-8679-9PCH 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-FJH6-8679-9PCH? flowise-ui (npm) versions < 3.0.10 is affected.
4. Is there a fix for GHSA-FJH6-8679-9PCH? Yes. GHSA-FJH6-8679-9PCH is fixed in 3.0.10. Upgrade to this version or later.
5. Is GHSA-FJH6-8679-9PCH exploitable, and should I be worried? Whether GHSA-FJH6-8679-9PCH 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-FJH6-8679-9PCH 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-FJH6-8679-9PCH? Upgrade flowise-ui to 3.0.10 or later.