CVE-2025-71328: Flowise Unverified Password Change Vulnerability (CVSS 8.3)

Technical summary

The vulnerability exists in Flowise's account settings Security section, where the password change function (PR:L, authenticated access required) fails to implement current-password verification before accepting a new credential. This violates fundamental account security practices and enables privilege escalation or lateral movement within shared Flowise deployments. The CVSS 3.1 score of 8.3 (HIGH) reflects high impact on confidentiality and integrity, combined with low attack complexity and no user interaction required once authenticated. CWE-620 (Unverified Password Change) is the root cause.

Business impact

An attacker with an active Flowise session can irreversibly change account passwords, blocking legitimate access and potentially exfiltrating sensitive data or workflows before locking out the owner. In multi-user or team deployments (common in enterprise AI orchestration), this can disrupt critical automation pipelines, compromise intellectual property embedded in workflows, and enable data theft. Recovery requires manual intervention from administrators, creating incident response overhead and potential downtime.

Affected systems

Flowise versions prior to 3.0.10 are affected. Organizations running Flowise on-premises or in cloud environments with shared access or session-sharing risks should prioritize inventory and patching. The vulnerability requires prior authentication, so attack surface is limited to users with valid credentials or those whose sessions can be compromised.

Exploitability

Exploitability is moderate-to-high. The barrier to entry is low attack complexity (AC:L) once an attacker has authenticated access, and no additional user interaction is needed. Real-world attack vectors include: (1) credential compromise via phishing or malware, (2) session hijacking on shared or poorly isolated networks, (3) insider threats, and (4) default or weak credentials. The vulnerability has not been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, but the simplicity of the attack—mere password change form submission—makes weaponization trivial.

Remediation

Upgrade Flowise to version 3.0.10 or later. Verify the upgrade by checking the version in the Flowise UI or logs. Until patched, implement access controls: restrict Flowise instances to trusted networks, enforce multi-factor authentication (MFA) if available, rotate credentials regularly, monitor account settings changes for suspicious activity, and restrict session lifetimes. Assume any account with unusual password-change events may have been compromised and force re-authentication.

Patch guidance

Deploy Flowise 3.0.10 or later from the official repository. Test the patch in a non-production environment first to confirm compatibility with your workflows and integrations. Coordinate the upgrade with end users to avoid disruption. After patching, force users to re-authenticate to invalidate any hijacked sessions from before the fix. If MFA is available, enable it organization-wide. Check release notes to ensure the patch applies to your deployment model (self-hosted, containerized, etc.).

Detection guidance

Monitor Flowise audit logs for: (1) password change events (especially from unexpected IP addresses or at unusual times), (2) rapid successive password changes by the same account, (3) account lockouts followed by password resets, (4) session creation and password change from different IP addresses within a short window. Alert on any password-change event that lacks a corresponding 'current password' validation in logs. Review failed authentication attempts before a successful password change—they may indicate credential-guessing or session hijacking. Correlate Flowise logs with network and endpoint logs to detect session abuse.

Why prioritize this

This is a HIGH-severity vulnerability (CVSS 8.3) that enables rapid account takeover with no user interaction required post-authentication. In a platform designed for orchestrating AI workflows and integrations, account compromise directly threatens data confidentiality, integrity, and business continuity. The simplicity of the exploit (no complex technical steps) and the absence of additional verification make it attractive to both opportunistic attackers and sophisticated threat actors. Prioritize patching within 30 days, especially for internet-facing or multi-user Flowise instances.

Risk score, explained

The CVSS 3.1 score of 8.3 reflects: (1) Network attack vector (AV:N)—accessible remotely once authenticated, (2) Low attack complexity (AC:L)—no special conditions or tools required, (3) Low privilege level (PR:L)—attacker needs valid credentials but no admin role, (4) No user interaction (UI:N)—the attacker controls the attack, (5) High confidentiality and integrity impact (C:H, I:H)—attacker can read and modify account data and workflows, (6) Low availability impact (A:L)—the legitimate user is locked out but the system itself remains functional. The score does not assume exploit availability in public databases, but the vulnerability's simplicity suggests rapid weaponization is likely.

Frequently asked questions