Account takeover via unverified password change
Published Jun 25, 2026 · Updated Jun 25, 2026
Unverified password change in Flowise before 3.0.10 allows remote authenticated users to take over an account through its Security settings. The account settings password-change flow accepts and applies a new password without checking the current password or requiring another verification factor. An attacker needs control of or influence over an authenticated session, but the changed credential can convert that temporary access into persistent account control.
Summary
What happened
Unverified password change in Flowise before 3.0.10 allows remote authenticated users to take over an account through its Security settings. The account settings password-change flow accepts and applies a new password without checking the current password or requiring another verification factor. An attacker needs control of or influence over an authenticated session, but the changed credential can convert that temporary access into persistent account control.
The record
- CVE
- CVE-2025-71328
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- CWE-306, CWE-620, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-fjh6-8679-9pch reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo