Advisoriesby IbisFlowise Fails to Invalidate Existing Sessions After Password Changes
Summary
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.
Impact
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...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| flowise npm | < 3.0.10 | 3.0.10 |
Details and references
### Summary 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. ### Impact 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
- CVSS 3.0
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-613
- Also known as
- CVE-2025-71335
More Flowise advisories
All Flowise
Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register)CVE-2025-71327no fix yetFlowise: Authenticated Command Execution and Sandbox Bypass via Puppeteer and Playwright PackagesCVE-2025-34267fixed in 3.0.8Flowise is vulnerable to arbitrary file exposure through its ReadFileToolGHSA-j44m-5v8f-gc9cfixed in 3.0.8Flowise is vulnerable to arbitrary file write through its WriteFileToolCVE-2025-61913fixed in 3.0.8FlowiseAI/Flosise has File Upload vulnerabilityCVE-2025-61687fixed in 3.0.8Flowise vulnerable to RCE via Dynamic function constructor injectionCVE-2025-55346no fix yet