GHSA-x39m-3393-3qp4: Flowise ui Flowise Doesn't Prevent Bypass Of Vulnerability

HIGH
Share
CVSS 8.3
CWE-620 CWE-306
Published
Advisory Summary

GHSA-x39m-3393-3qp4 is a HIGH (CVSS 8.3) flowise doesn't prevent bypass of vulnerability (CWE-620: Unverified Password Change) affecting Flowise ui libraries in the npm ecosystem. The issue involves flowise doesn't prevent bypass of password confirmation through unverified email change (credentials). Remediation is available by upgrading affected packages to version 3.0.10.

GHSA-x39m-3393-3qp4 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-x39m-3393-3qp4
Severity HIGH
CVSS v3.1 Base Score 8.3
CWE Classification CWE-620: Unverified Password Change
Affected Product Flowise ui
Package Ecosystem npm
Published Date
Last Updated

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).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability Low (A:L)

How to Fix GHSA-x39m-3393-3qp4

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.

flowise-ui fixed: 3.0.10 
npm install flowise-ui@3.0.10
Verify Direct and Transitive Dependencies

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-x39m-3393-3qp4, 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

### 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:** 1. As logged in user https://cloud.flowiseai.com/account scroll down to 'Profile' section 2. Change email to the new email 3. 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** <img width="329" height="357" alt="secbug" src="https://github.com/user-attachments/assets/d3c77835-35bb-47dc-8cd2-83e4e266e5a4" /> ### 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)

GHSA-x39m-3393-3qp4 Affected Flowise ui Versions

1 component(s)
Fixed Versions:
3.0.10
Product / Package Ecosystem Affected Versions Fixed Version
flowise-ui
npm/flowise-ui
npm
< 3.0.10
3.0.10

References

Flowise ui Source Repository REPOSITORY
https://github.com/FlowiseAI/Flowise/pull/5294
GitHub Advisory / Wiki ADVISORY
https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-x39m-3393-3qp4
Flowise ui Source Repository REPOSITORY
https://github.com/FlowiseAI/Flowise
Flowise ui Release RELEASE
https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.10

Frequently Asked Questions

What is GHSA-x39m-3393-3qp4?
GHSA-x39m-3393-3qp4 is a security vulnerability in Flowise ui involving Flowise doesn't Prevent Bypass of Password Confirmation through Unverified Email Change (credentials) under CWE-620: Unverified Password Change.
Which Flowise ui versions are affected?
Affected versions include releases prior to 3.0.10 across affected packages: flowise-ui.
What version fixes GHSA-x39m-3393-3qp4?
Upgrading to 3.0.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise-ui affected?
Yes, flowise-ui is affected in releases prior to 3.0.10. Upgrade your dependency to 3.0.10 or later.
What is the CVSS score of GHSA-x39m-3393-3qp4?
GHSA-x39m-3393-3qp4 has a CVSS v3.1 base score of 8.3 (HIGH) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with GHSA-x39m-3393-3qp4?
GHSA-x39m-3393-3qp4 is classified under CWE-620: Unverified Password Change (When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.).
How can I check npm dependencies for GHSA-x39m-3393-3qp4?
Run the dependency tree command: 'npm ls flowise-ui'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x39m-3393-3qp4",
  "modified" : "2025-11-14T20:56:02Z",
  "published" : "2025-11-14T20:56:02Z",
  "aliases" : [ ],
  "summary" : "Flowise doesn't Prevent Bypass of Password Confirmation through Unverified Email Change (credentials)",
  "details" : "### Summary\nUnverified Email Change - Email as part of Credential / Unverified Account Recovery Channel Change\n\nThe 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.\n\n### Details\nOccurence - code:\nhttps://github.com/FlowiseAI/Flowise/blob/main/packages/ui/src/views/account/index.jsx#L211\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 'Profile' section\n2. Change email to the new email\n3. Notice Unverified Password Change (authenticated change without current password)\n\nLater this email is needed as credentials to log in or reset password feature.\n\n**POC:**\nEmail changed, and notice \"Profile updated\" message.\n\n**Screenshot**\n<img width=\"329\" height=\"357\" alt=\"secbug\" src=\"https://github.com/user-attachments/assets/d3c77835-35bb-47dc-8cd2-83e4e266e5a4\" />\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 password - 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-x39m-3393-3qp4"
  }, {
    "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:56:02Z",
    "nvd_published_at" : null
  }
}