How severe is GHSA-2364-jh4q-m9vm?

No CVSS score has been assigned to GHSA-2364-jh4q-m9vm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2364-jh4q-m9vm?

GHSA-2364-jh4q-m9vm affects the following packages: flowise (npm). Ecosystems affected: npm.

How do I fix GHSA-2364-jh4q-m9vm?

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.

How do I detect GHSA-2364-jh4q-m9vm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2364-jh4q-m9vm if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-2364-jh4q-m9vm actively exploited in the wild?

No public exploit code has been indexed for GHSA-2364-jh4q-m9vm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-2364-jh4q-m9vm?

GHSA-2364-jh4q-m9vm has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 29th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2364-jh4q-m9vm?

GHSA-2364-jh4q-m9vm is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2364-jh4q-m9vm published, and has it been updated?

GHSA-2364-jh4q-m9vm was published on August 4, 2026 and was last updated on August 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Flowise: IDOR vulnerability exists at the GET /api/v1/organization/customer-default-source endpointGHSA-2364-jh4q-m9vm

Fix: FlowiseAI/Flowise#6321

GHSA-2364-jh4q-m9vm is a CWE-639 vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.

Also known asCVE-2026-73488

Published

Aug 4, 2026

Updated

Aug 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2364-jh4q-m9vm.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

flowisenpm

3Kdownloads / week

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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`flowise`	all versions	3.1.3`npm install flowise@3.1.3`

Affected Products

1 product · 1 configurations

Application

flowiseflowiseai

< 3.1.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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 ver

O3 Security · Impact-Aware SCA

Is GHSA-2364-jh4q-m9vm in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works