GHSA-2364-jh4q-m9vm
GHSA-2364-jh4q-m9vm is a security vulnerability in flowise. O3 Security confirms whether GHSA-2364-jh4q-m9vm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpoint
Blast Radius
flowiseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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
-
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 3.1.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update flowise to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2364-jh4q-m9vm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2364-jh4q-m9vm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2364-jh4q-m9vm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2364-jh4q-m9vm in your dependencies?
O3 detects GHSA-2364-jh4q-m9vm across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.