Summary
Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint
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
To reproduce the vulnerability, follow these steps:
Log in to your account at cloud.flowiseai.com.
Capture a request to the payment source endpoint using a proxy tool (e.g., Burp Suite).
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": "[email protected]",
"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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2364-JH4Q-M9VM? GHSA-2364-JH4Q-M9VM is a medium-severity security vulnerability in flowise (npm), affecting versions <= 3.1.2. It is fixed in 3.1.3.
- Which versions of flowise are affected by GHSA-2364-JH4Q-M9VM? flowise (npm) versions <= 3.1.2 is affected.
- Is there a fix for GHSA-2364-JH4Q-M9VM? Yes. GHSA-2364-JH4Q-M9VM is fixed in 3.1.3. Upgrade to this version or later.
- Is GHSA-2364-JH4Q-M9VM exploitable, and should I be worried? Whether GHSA-2364-JH4Q-M9VM is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2364-JH4Q-M9VM is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2364-JH4Q-M9VM? Upgrade
flowiseto 3.1.3 or later.