GHSA-48m6-ch88-55mj — flowise
HIGHGHSA-48m6-ch88-55mj is a high-severity (CVSS 8.1) CWE-639 vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.
Flowise: Improper Mass Assignment in Account Registration Enables Unauthorized Organization Association
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-48m6-ch88-55mj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
flowisenpmDescription
Summary
An improper mass assignment (JSON injection) vulnerability in the account registration endpoint of Flowise Cloud allows unauthenticated attackers to inject server-managed fields and nested objects during account creation. This enables client-controlled manipulation of ownership metadata, timestamps, organization association, and role mappings, breaking trust boundaries in a multi-tenant environment.
Details
The POST /api/v1/account/register endpoint is intended to accept a minimal payload to create a new user account (e.g., name, email, password). However, the backend fails to enforce a strict allowlist or DTO-based validation and instead blindly maps client-supplied JSON to internal domain models.
As a result, attackers can include additional nested objects and server-managed fields in the request body such as organization, organizationUser, workspace, workspaceUser, and metadata fields like createdBy, updatedBy, createdDate, and updatedDate. These fields are persisted as provided by the client rather than being generated or validated server-side.
This behavior demonstrates a trust boundary violation where authorization and ownership decisions that must be enforced by the server are effectively delegated to untrusted client input. In a multi-tenant SaaS context, this can lead to unauthorized organization association and role assignment during registration.
PoC
Send a standard registration request:
POST /api/v1/account/register HTTP/2
Host: cloud.flowiseai.com
Content-Type: application/json
{
"user": {
"name": "Test User",
"email": "[email protected]",
"credential": "StrongPassword123!"
}
}
Observe the 201 Created response returning a newly created user and related objects (organization, workspace, roles).
Send a modified registration request that injects additional server-managed fields and nested objects:
POST /api/v1/account/register HTTP/2 Host: cloud.flowiseai.com Content-Type: application/json
{
"user": {
"name": "Injected User",
"email": "[email protected]",
"credential": "StrongPassword123!",
"createdBy": "<arbitrary-uuid>",
"updatedBy": "<arbitrary-uuid>",
"createdDate": "1999-12-27T13:10:47.666Z",
"updatedDate": "1999-12-27T13:10:47.666Z"
},
"organization": {
"id": "<existing-organization-uuid>",
"name": "Injected Organization"
},
"organizationUser": {
"organizationId": "<existing-organization-uuid>",
"roleId": "<owner-role-uuid>"
}
}
Observe that the server responds with 201 Created and persists the injected fields, reflecting client-controlled values for ownership metadata, timestamps, and organization association.
Impact
- Vulnerability Class: Mass Assignment / JSON Injection / Improper Input Validation.
- Who is impacted: All deployments of Flowise Cloud exposing the registration endpoint.
By supplying a known organizationId during registration, an unauthenticated attacker can create a new user account directly associated with an existing organization they do not belong to. This results in unauthorized cross-tenant access and privilege escalation at account creation time, completely bypassing organizational ownership and trust boundaries.
Security Consequences:
- Client-controlled manipulation of server-managed fields (audit timestamps, ownership metadata).
- Unauthorized association of newly created accounts with existing organizations.
- Injection of role and membership relationships during registration.
- Violation of trust boundaries in a multi-tenant environment, increasing the risk of privilege abuse and audit integrity failures.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 3.1.0npm install flowise@3.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48m6-ch88-55mj 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-48m6-ch88-55mj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-48m6-ch88-55mj. 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-48m6-ch88-55mj in your dependencies?
O3 Security finds GHSA-48m6-ch88-55mj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.