GHSA-X7RP-QJ2H-GHGW

Failure to Invalidate Existing Sessions After Password Change (Persistent Session / Session Invalidity Failure).

Details

After a user changes their password, the application does not invalidate other active sessions or session tokens that were established before the change. An attacker who already has an active session (e.g., via a stolen session token, device left logged in, or other access) continues to be authenticated even after the legitimate user rotates credentials, allowing the attacker to retain access despite the user’s password change.

PoC

Repro steps:

1. As logged in user on two browsers (ie. Chrome and Firefox, with incognito/private mode) https://cloud.flowiseai.com/account change password, on the Chrome for example
2. Refresh the site on Firefox (second browser) - notice that still logged in (despite credentials were changed)

POC:
Steps described above (in Repro steps) completed successfully.

Persistent unauthorized access despite credential rotation - undermines the primary purpose of password changes as a remediation step.
Enables attackers with an active session (remote or physical access to a device) to continue acting as the user (confidentiality and integrity impact).
If session tokens are not bound to the credential state, forced password changes won’t terminate attacker sessions.

Resources
OWASP Session Management Cheat Sheet
CWE-613: Insufficient Session Expiration

GHSA-X7RP-QJ2H-GHGW has a CVSS score of 8.1 (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-X7RP-QJ2H-GHGW? GHSA-X7RP-QJ2H-GHGW is a high-severity security vulnerability in flowise (npm), affecting versions < 3.0.10. It is fixed in 3.0.10.
2. How severe is GHSA-X7RP-QJ2H-GHGW? GHSA-X7RP-QJ2H-GHGW has a CVSS score of 8.1 (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 are affected by GHSA-X7RP-QJ2H-GHGW? flowise (npm) versions < 3.0.10 is affected.
4. Is there a fix for GHSA-X7RP-QJ2H-GHGW? Yes. GHSA-X7RP-QJ2H-GHGW is fixed in 3.0.10. Upgrade to this version or later.
5. Is GHSA-X7RP-QJ2H-GHGW exploitable, and should I be worried? Whether GHSA-X7RP-QJ2H-GHGW 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-X7RP-QJ2H-GHGW 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-X7RP-QJ2H-GHGW? Upgrade flowise to 3.0.10 or later.