GHSA-2364-jh4q-m9vm: Flowise Remote Code Execution Vulnerability

MODERATE
CWE-639
Published
Advisory Summary

GHSA-2364-jh4q-m9vm is a MODERATE remote code execution vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Flowise libraries in the npm ecosystem. The issue involves idor vulnerability exists at the get /api/v1/organization/customer-default-source endpoint. Remediation is available by upgrading affected packages to version 3.1.3.

GHSA-2364-jh4q-m9vm at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-2364-jh4q-m9vm
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Flowise
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-2364-jh4q-m9vm

To remediate this vulnerability, upgrade all affected Flowise 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 fixed: 3.1.3
npm install flowise@3.1.3
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

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-2364-jh4q-m9vm, inspect your project dependencies using npm:

npm ls flowise

Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.3), your application is affected.

Note: The npm ls flowise 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-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Flowise, 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 An Insecure Direct Object Reference (IDOR) vulnerability exists at the **GET /api/v1/organization/customer-default-source** endpoint. This flaw allows an authenticated attacker to bypass authorization checks and retrieve sensitive payment and profile information of other customers by manipulating the customerId parameter. The exposed data includes email addresses, account balances, currency types, and internal billing configurations. ### Details The application fails to implement proper object-level access control. While the endpoint requires a valid session/token, it does not verify if the requesting user has the authority to access the specific customerId provided in the query string. When a request is made to: GET /api/v1/organization/customer-default-source?customerId=cus_XXXX The server processes the request based solely on the existence of a valid session, returning the data associated with the ID regardless of the data owner's identity. Since customer IDs follow a predictable pattern (Stripe-formatted cus_...), an attacker could potentially enumerate these IDs to scrape customer data. ### PoC 1. To reproduce the vulnerability, follow these steps: 2. Log in to your account at cloud.flowiseai.com. 3. Capture a request to the payment source endpoint using a proxy tool (e.g., Burp Suite). 4. Change the customerId parameter in the URL to a target user's ID (e.g., cus_U9ajkQvu0e67uH). Execute the request: ``` GET /api/v1/organization/customer-default-source?customerId=cus_U9ajkQvu0e67uH HTTP/2 Host: cloud.flowiseai.com Cookie: [YOUR_AUTHENTICATED_COOKIES] ... ``` Response: ``` { "id": "cus_U9ajkQvu0e67uH", "object": "customer", "email": "truongnguyen210044@gmail.com", "balance": 0, "currency": "usd", "invoice_settings": { "custom_fields": null, "default_payment_method": null }, "livemode": true ... } ``` The server returns a 200 OK status with the private data of the target customer. ### Impact - Vulnerability Type: Broken Access Control (IDOR). - Impacted Parties: All registered users and organizations on the FlowiseAI Cloud platform. - Consequences: * Data Privacy Breach: Exposure of Personally Identifiable Information (PII) such as email addresses. - Financial Information Leakage: Disclosure of account balances, currency settings, and invoice metadata. - Compliance Risk: Potential violation of data protection regulations (e.g., GDPR) due to unauthorized access to user billing profiles.

GHSA-2364-jh4q-m9vm Affected Flowise Versions

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

References

Frequently Asked Questions

What is GHSA-2364-jh4q-m9vm?
GHSA-2364-jh4q-m9vm is a security vulnerability in Flowise involving IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Flowise versions are affected?
Affected versions include releases prior to 3.1.3 across affected packages: flowise.
What version fixes GHSA-2364-jh4q-m9vm?
Upgrading to 3.1.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is flowise affected?
Yes, flowise is affected in releases prior to 3.1.3. Upgrade your dependency to 3.1.3 or later.
What CWE is associated with GHSA-2364-jh4q-m9vm?
GHSA-2364-jh4q-m9vm is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check npm dependencies for GHSA-2364-jh4q-m9vm?
Run the dependency tree command: 'npm ls flowise'. 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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2364-jh4q-m9vm",
  "modified" : "2026-08-04T14:16:46Z",
  "published" : "2026-08-04T14:16:46Z",
  "aliases" : [ ],
  "summary" : "Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint",
  "details" : "### Summary\nAn Insecure Direct Object Reference (IDOR) vulnerability exists at the **GET /api/v1/organization/customer-default-source** endpoint. This flaw allows an authenticated attacker to bypass authorization checks and retrieve sensitive payment and profile information of other customers by manipulating the customerId parameter. The exposed data includes email addresses, account balances, currency types, and internal billing configurations.\n\n### Details\nThe application fails to implement proper object-level access control. While the endpoint requires a valid session/token, it does not verify if the requesting user has the authority to access the specific customerId provided in the query string.\n\nWhen a request is made to:\nGET /api/v1/organization/customer-default-source?customerId=cus_XXXX\n\nThe server processes the request based solely on the existence of a valid session, returning the data associated with the ID regardless of the data owner's identity. Since customer IDs follow a predictable pattern (Stripe-formatted cus_...), an attacker could potentially enumerate these IDs to scrape customer data.\n\n### PoC\n1. To reproduce the vulnerability, follow these steps:\n\n2. Log in to your account at cloud.flowiseai.com.\n\n3. Capture a request to the payment source endpoint using a proxy tool (e.g., Burp Suite).\n\n4. Change the customerId parameter in the URL to a target user's ID (e.g., cus_U9ajkQvu0e67uH).\n\nExecute the request:\n```\nGET /api/v1/organization/customer-default-source?customerId=cus_U9ajkQvu0e67uH HTTP/2\nHost: cloud.flowiseai.com\nCookie: [YOUR_AUTHENTICATED_COOKIES]\n...\n```\nResponse: \n```\n{\n  \"id\": \"cus_U9ajkQvu0e67uH\",\n  \"object\": \"customer\",\n  \"email\": \"truongnguyen210044@gmail.com\",\n  \"balance\": 0,\n  \"currency\": \"usd\",\n  \"invoice_settings\": {\n    \"custom_fields\": null,\n    \"default_payment_method\": null\n  },\n  \"livemode\": true\n  ...\n}\n```\nThe server returns a 200 OK status with the private data of the target customer.\n### Impact\n- Vulnerability Type: Broken Access Control (IDOR).\n\n- Impacted Parties: All registered users and organizations on the FlowiseAI Cloud platform.\n\n- Consequences: * Data Privacy Breach: Exposure of Personally Identifiable Information (PII) such as email addresses.\n- Financial Information Leakage: Disclosure of account balances, currency settings, and invoice metadata.\n\n- Compliance Risk: Potential violation of data protection regulations (e.g., GDPR) due to unauthorized access to user billing profiles.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "flowise"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 3.1.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-2364-jh4q-m9vm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/pull/6321"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/commit/4d7899d02ca370a5510406be5c91483085a412f9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/FlowiseAI/Flowise"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.1.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-04T14:16:46Z",
    "nvd_published_at" : null
  }
}