Cyber Resilience

CVE-2025-71328

Flowiseai Flowise ≤ 3.0.10

Public PoC
Published
25 June 2026
Modified
29 June 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0040 33th percentile
Risk Priority 39 floored blend · peak EPSS

Summary

CVE-2025-71328 is a high-severity Unverified Password Change (CWE-620) vulnerability in Flowiseai Flowise. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Account Manipulation (T1098); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to IA-11 (Re-authentication) and IA-5 (Authenticator Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

check on the credential change. This can lead to full account takeover, particularly if an attacker can hijack or coerce an authenticated session.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1098 Account Manipulation Persistence
Adversaries may manipulate accounts to maintain and/or elevate access to victim systems.
T1098.001 Additional Cloud Credentials Persistence
Adversaries may add adversary-controlled credentials to a cloud account to maintain persistent access to victim accounts and instances within the environment.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-71337Same product: Flowiseai Flowise
CVE-2024-8181Same product: Flowiseai Flowise
CVE-2025-71332Same product: Flowiseai Flowise
CVE-2026-56277Same product: Flowiseai Flowise
CVE-2026-56270Same product: Flowiseai Flowise
CVE-2026-56275Same product: Flowiseai Flowise
CVE-2026-56268Same product: Flowiseai Flowise
CVE-2025-71335Same product: Flowiseai Flowise
CVE-2024-31621Same product: Flowiseai Flowise
CVE-2025-71338Same product: Flowiseai Flowise

Affected Assets

flowiseai
flowise
≤ 3.0.10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Re-authentication explicitly requires users to prove identity before performing sensitive actions such as password changes.

Authenticator management requires identity verification during password distribution and changes, directly stopping unverified password updates.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 mostly match
prevents

Credential management practices directly enforce re-authentication for password changes.

PR.AA-03 mostly match
prevents

Authentication requirements include verifying identity before allowing credential modifications.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

degrades

Requires secure management of authentication information, directly addressing the need to verify the original password before allowing a change.

prevents

Mandates secure authentication mechanisms, which include verifying existing credentials before permitting password changes.

none

Identity management processes can incorporate verification steps, but the control itself does not explicitly require password-change verification.

none

Information access restriction can be strengthened by password verification, yet the control focuses on access rights rather than change procedures.

References