CVE-2025-71328: Flowise - Unverified Password Change via Account Settings
Flowise before 3.0.10 contains an unverified password change vulnerability. An authenticated user can change their account password through the account settings (Security) section without supplying the current password or any additional verification, as the application does not enforce a current-password check on the credential change. This can lead to full account takeover, particularly if an attacker can hijack or coerce an authenticated session.
Security readout for executives and security teams
Plain-English summary
Flowise versions before 3.0.10 allow a logged-in user session to change the account password without re-entering the current password. If an attacker gains access to an authenticated session, this weakness can help turn temporary access into account takeover. No active exploitation is cited in the provided sources.
Executive priority
Treat as high priority for Flowise environments. The issue can convert session compromise into durable account control. Patch promptly, especially for externally reachable or business-critical Flowise instances, but do not assume active exploitation without further evidence.
Technical view
CVE-2025-71328 is a CWE-620 unverified password change issue in Flowise before 3.0.10. The account settings Security flow does not enforce current-password or additional verification before credential change. CVSS v4.0 is 8.7, with network attack vector, low complexity, and low privileges required.
Likely exposure
Organizations running Flowise before 3.0.10 are potentially exposed. Risk is higher where Flowise is internet-accessible, shared by multiple users, or where session theft, browser compromise, or coerced authenticated actions are plausible.
Exploitation context
The provided sources describe abuse by an authenticated user or someone controlling an authenticated session. They do not cite public exploitation, KEV listing, exploit code, or widespread attacks. The main concern is account takeover following session hijack or misuse.
Researcher notes
Source evidence supports Flowise before 3.0.10, CVSS 8.7, and CWE-620. The bundle does not provide detailed exploit artifacts or indicators of compromise. Validate behavior defensively and rely on vendor advisory details for exact fixed-version guidance.
Mitigation direction
Upgrade Flowise to 3.0.10 or later, based on vendor advisory scope.
Review the GitHub Security Advisory for any additional vendor instructions.
Limit Flowise access to trusted networks or approved identity paths.
Invalidate suspicious sessions and rotate affected account credentials where exposure is suspected.
Monitor for unexpected password changes in Flowise accounts.
Validation and detection
Inventory all Flowise deployments and record running versions.
Confirm any version before 3.0.10 is prioritized for remediation.
In a controlled test, verify password changes require current-password or equivalent verification.
Review logs for password changes followed by unusual access patterns.
Check whether Flowise administrative interfaces are exposed beyond intended users.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-620: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-620 · source CWE mapping
Unverified Password Change
Unverified Password Change represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.