Vulnerabilities in pkg:npm/flowise-ui
PACKAGEGHSA-fjh6-8679-9pch is a HIGH (CVSS 8.3) flowise does not prevent bypass vulnerability (CWE-620: Unverified Password Change) affecting Flowise ui libraries in the npm ecosystem. The issue involves flowise does not prevent bypass of password confirmation - unverified password change. Remediation is available by upgrading affected packages to version 3.0.10.
pkg:npm/flowise-ui
Vulnerability advisories affecting package pkg:npm/flowise-ui. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-fjh6-8679-9pch | - | HIGH | Flowise does not Prevent Bypass of Password Confirmation - Unverified Password Change |
| GHSA-x39m-3393-3qp4 | - | HIGH | Flowise doesn't Prevent Bypass of Password Confirmation through Unverified Email Change (credentials) |
GHSA-fjh6-8679-9pch at a Glance
Security Impact
CVSS: 8.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L).
How to Fix GHSA-fjh6-8679-9pch
To remediate this vulnerability, upgrade all affected Flowise ui dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install flowise-ui@3.0.10
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls flowise-ui
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-fjh6-8679-9pch, inspect your project dependencies using npm:
npm ls flowise-ui
Analyze the terminal output to locate any version of Flowise ui in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.10), your application is affected.
Note: The npm ls flowise-ui command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-620: Unverified Password Change, where when setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication. In Flowise ui, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
GHSA-fjh6-8679-9pch Affected Flowise ui Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
flowise-ui
|
npm |
< 3.0.10
|
3.0.10
|
References
Frequently Asked Questions
What is GHSA-fjh6-8679-9pch?
Which Flowise ui versions are affected?
What version fixes GHSA-fjh6-8679-9pch?
Is flowise-ui affected?
What is the CVSS score of GHSA-fjh6-8679-9pch?
What CWE is associated with GHSA-fjh6-8679-9pch?
How can I check npm dependencies for GHSA-fjh6-8679-9pch?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-fjh6-8679-9pch",
"modified" : "2025-11-14T20:57:31Z",
"published" : "2025-11-14T20:57:31Z",
"aliases" : [ ],
"summary" : "Flowise does not Prevent Bypass of Password Confirmation - Unverified Password Change",
"details" : "### Summary\nBypass of Password Confirmation - Unverified Password Change (authenticated change without current password)\n\nAn authenticated user is allowed to change their account password without supplying the current password or any additional verification. The application does not verify the actor’s authority to perform that credential change (no current-password check, no authorization enforcement). An attacker who is merely authenticated (or who can trick or coerce an authenticated session) can set a new password and gain control of the account. (ATO - Account Takeover)\n\n### Details\nOccurence - code:\nhttps://github.com/FlowiseAI/Flowise/blob/main/packages/ui/src/views/account/index.jsx#L278 \n\nRemote and physical scenarios can be considered.\n\n### PoC\n**Repro steps:**\n1. As logged in user https://cloud.flowiseai.com/account scroll down to 'Security' section\n2. Change password to the new password\n3. Notice Unverified Password Change (authenticated change without current password)\n\n**POC:** \nPassword changed, and notice \"Password updated\" message.\n\n**Screenshot:**\n<img width=\"467\" height=\"526\" alt=\"secpw\" src=\"https://github.com/user-attachments/assets/4cc52978-9f37-42ca-a2b2-7285c4da9f1c\" />\n\n\n### Impact\nFull account takeover (ATO) of affected accounts (loss of confidentiality and integrity of account data).\nUser 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 email - part of credentials). (gain persistence)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "flowise-ui"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.0.10"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-fjh6-8679-9pch"
}, {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/pull/5294"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/FlowiseAI/Flowise"
}, {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.10"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-306", "CWE-620" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-11-14T20:57:31Z",
"nvd_published_at" : null
}
}