Vulnerability in flowise-ui (CVE-2025-71337)
Summary
Vulnerability in flowise-ui (CVE-2025-71337). Confidential information can be exposed externally. Mitigation: upgrade to 3.0.10 or later.
Original description
The description as published by the source.
Summary
Unverified Email Change - Email as part of Credential / Unverified Account Recovery Channel Change
The application allows changing the account email address (used as a login identifier and/or password recovery address) without verifying the requester’s authority to make that change (no confirmation to the old email, no authentication step). Because email often functions as a credential or recovery channel, unverified email changes enable attackers to take over accounts by switching the account’s recovery/login address.
Details
Occurence - code:
https://github.com/FlowiseAI/Flowise/blob/main/packages/ui/src/views/account/index.jsx#L211
Remote and physical scenarios can be considered.
PoC
Repro steps:
- As logged in user https://cloud.flowiseai.com/account scroll down to 'Profile' section
- Change email to the new email
- Notice Unverified Password Change (authenticated change without current password)
Later this email is needed as credentials to log in or reset password feature.
POC:
Email changed, and notice "Profile updated" message.
Screenshot
Impact
Full account takeover (ATO) of affected accounts (loss of confidentiality and integrity of account data).
User account recovery mechanisms (password reset flows tied to email) can be bypassed or abused if combined with this issue and the second one which I've reported (similar security issue with the password - part of credentials). (gain persistence)
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-71337 has been found in flowise-ui.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade flowise-ui to 3.0.10 or later.
If unsure, ask your IT team or search "flowise-ui CVE-2025-71337" on the vendor's site.
CVE-2025-71337 (flowise-ui) — CWE-620 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.0.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-620) exists in flowise-ui.
Check the vendor advisory for the affected versions of flowise-ui.
Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.
Update to 3.0.10.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flowise-ui' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flowise-ui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flowise-uiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flowise-ui to 3.0.10ステージング環境で 3.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- exploit github.com
- package github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com