Security readout for executives and security teams
Plain-English summary
Flowise has an account security flaw where a logged-in user can change an account email without proving control of the old email or re-entering the password. Because that email is used for login and password recovery, the issue can enable account takeover through recovery workflows.
Executive priority
Treat this as high priority where Flowise is internet-facing, multi-user, or used for sensitive automation. The business risk is account takeover, not just profile tampering.
Technical view
CVE-2025-71337 affects Flowise versions identified as before 3.0.10, specifically 3.0.7 and earlier in the provided record. The account profile endpoint allows unverified email changes. The CVSS 4.0 score is 8.7, with network access, low privileges, low complexity, and high confidentiality and integrity impact.
Likely exposure
Organizations running Flowise 3.0.7 or earlier, or any deployment matching the vendor advisory's affected range, are likely exposed if authenticated users can access profile settings.
Exploitation context
The sources describe abuse by an authenticated user and password reset mechanisms. The provided bundle does not show CISA KEV listing or public evidence of active exploitation.
Researcher notes
This is CWE-620: unverified password change or account recovery data change. The key exposure condition is authenticated access to the profile endpoint. Evidence is limited to the provided CVE, GitHub advisory, and VulnCheck advisory.
Mitigation direction
- Upgrade Flowise to 3.0.10 or later, following vendor guidance.
- Confirm the vendor advisory's affected range against deployed Flowise versions.
- Review account recovery and email-change policies for administrative users.
- Temporarily restrict access to Flowise accounts where untrusted users exist.
- Monitor for unexpected email changes and password reset activity.
Validation and detection
- Inventory all Flowise deployments and record exact versions.
- Check whether affected instances are 3.0.7 or earlier.
- Review audit logs for recent account email changes.
- Correlate email changes with password reset events.
- Confirm upgraded instances require proper verification for email changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCredential and access behavior lookup
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.
Open ATT&CK lookupCVE-2025-71337 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L2.85.5VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-x39m-3393-3qp4)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Unverified Email Change via Account Profile EndpointCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unverified Password Change
Unverified Password Change represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.