Skip to content

Commit bcf3b02

Browse files
advisory-database[bot]advisory-database[bot]
committed
Publish Advisories
GHSA-48m6-ch88-55mj GHSA-4jpm-cgx2-8h37 GHSA-9wc7-mj3f-74xv GHSA-f228-chmx-v6j6
1 parent add3963 commit bcf3b02

4 files changed

Lines changed: 280 additions & 0 deletions

File tree

‎advisories/github-reviewed/2026/04/GHSA-48m6-ch88-55mj/GHSA-48m6-ch88-55mj.json‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-48m6-ch88-55mj",
4+
"modified": "2026-04-16T21:44:24Z",
5+
"published": "2026-04-16T21:44:24Z",
6+
"aliases": [],
7+
"summary": "Flowise: Improper Mass Assignment in Account Registration Enables Unauthorized Organization Association",
8+
"details": "### Summary\n\nAn 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.\n\n### Details\n\nThe 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.\n\nAs 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.\n\nThis 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.\n\n### PoC\nSend a standard registration request:\n\n```http\nPOST /api/v1/account/register HTTP/2\nHost: cloud.flowiseai.com\nContent-Type: application/json\n\n{\n \"user\": {\n \"name\": \"Test User\",\n \"email\": \"testuser@example.com\",\n \"credential\": \"StrongPassword123!\"\n }\n}\n```\n\n\nObserve the 201 Created response returning a newly created user and related objects (organization, workspace, roles).\n\nSend a modified registration request that injects additional server-managed fields and nested objects:\n\nPOST /api/v1/account/register HTTP/2\nHost: cloud.flowiseai.com\nContent-Type: application/json\n\n```http\n{\n \"user\": {\n \"name\": \"Injected User\",\n \"email\": \"injected@example.com\",\n \"credential\": \"StrongPassword123!\",\n \"createdBy\": \"<arbitrary-uuid>\",\n \"updatedBy\": \"<arbitrary-uuid>\",\n \"createdDate\": \"1999-12-27T13:10:47.666Z\",\n \"updatedDate\": \"1999-12-27T13:10:47.666Z\"\n },\n \"organization\": {\n \"id\": \"<existing-organization-uuid>\",\n \"name\": \"Injected Organization\"\n },\n \"organizationUser\": {\n \"organizationId\": \"<existing-organization-uuid>\",\n \"roleId\": \"<owner-role-uuid>\"\n }\n}\n```\n\n\nObserve that the server responds with 201 Created and persists the injected fields, reflecting client-controlled values for ownership metadata, timestamps, and organization association.\n\n### Impact\n- Vulnerability Class: Mass Assignment / JSON Injection / Improper Input Validation.\n- Who is impacted: All deployments of Flowise Cloud exposing the registration endpoint.\n\nBy 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.\n\n**Security Consequences**:\n\n1. Client-controlled manipulation of server-managed fields (audit timestamps, ownership metadata).\n2. Unauthorized association of newly created accounts with existing organizations.\n3. Injection of role and membership relationships during registration.\n4. Violation of trust boundaries in a multi-tenant environment, increasing the risk of privilege abuse and audit integrity failures.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V3",
12+
"score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "npm",
19+
"name": "flowise"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "3.1.0"
30+
}
31+
]
32+
}
33+
],
34+
"database_specific": {
35+
"last_known_affected_version_range": "<= 3.0.13"
36+
}
37+
}
38+
],
39+
"references": [
40+
{
41+
"type": "WEB",
42+
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-48m6-ch88-55mj"
43+
},
44+
{
45+
"type": "PACKAGE",
46+
"url": "https://github.com/FlowiseAI/Flowise"
47+
}
48+
],
49+
"database_specific": {
50+
"cwe_ids": [
51+
"CWE-20",
52+
"CWE-639",
53+
"CWE-915"
54+
],
55+
"severity": "HIGH",
56+
"github_reviewed": true,
57+
"github_reviewed_at": "2026-04-16T21:44:24Z",
58+
"nvd_published_at": null
59+
}
60+
}

‎advisories/github-reviewed/2026/04/GHSA-4jpm-cgx2-8h37/GHSA-4jpm-cgx2-8h37.json‎

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-4jpm-cgx2-8h37",
4+
"modified": "2026-04-16T21:44:49Z",
5+
"published": "2026-04-16T21:44:49Z",
6+
"aliases": [],
7+
"summary": "Flowise: Sensitive Data Leak in public-chatbotConfig ",
8+
"details": "### Summary\n\n`/api/v1/public-chatbotConfig/:id `ep exposes sensitive data including API keys, HTTP authorization headers and internal configuration without any authentication. An attacker with knowledge just of a chatflow UUID can retrieve credentials stored in password type fields and HTTP headers, leading to credential theft and more.\n\n### Details\n\nKnowledge of chatflow UUID can be obtained from embedded chat widgets, referrer headers or logs and it's the only prerequest. \n\n`getSinglePublicChatbotConfig` function in `packages/server/src/services/chatflows/index.ts` returns the full **flowData** object without authorization check or data sanitization.\n\nThere is a comment as **\"Safe as public endpoint as chatbotConfig doesn't contain sensitive credential\"** but **flowData** does contain sensitive data such as:\n\n`type: 'password'` fields are stored in plaintext (unstructuredAPIKey in S3File node).\nHTTP Authorization headers in POST / GET Requests nodes.\nInternal API endpoints and webhook URLs.\n\n### PoC\n\n- Add an S3 File node, set \"File Processing Method\" to \"Unstructured\".\n- Enter an API key in \"Unstructured API KEY\" field or add a Requests Post node with Authorization header.\n- Save the chatflow.\n\n`curl -s \"https://localhost/api/v1/public-chatbotConfig/{CHATFLOW_UUID}\"`\n\nResponse:\n\n```\n{\n \"flowData\": \"{...\\\"unstructuredAPIKey\\\":\\\"victim_key\\\"...\\\"requestsPostHeaders\\\":\\\"Bearer victim_token\\\"...}\"\n}\n```\n\n### Impact\n\nImpacts all Flowise Cloud users with chatflows containing password type fields or any HTTP headers. And self hosted Flowise instances exposed to the internet.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "npm",
19+
"name": "flowise"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "3.1.0"
30+
}
31+
]
32+
}
33+
],
34+
"database_specific": {
35+
"last_known_affected_version_range": "<= 3.0.13"
36+
}
37+
}
38+
],
39+
"references": [
40+
{
41+
"type": "WEB",
42+
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-4jpm-cgx2-8h37"
43+
},
44+
{
45+
"type": "PACKAGE",
46+
"url": "https://github.com/FlowiseAI/Flowise"
47+
}
48+
],
49+
"database_specific": {
50+
"cwe_ids": [
51+
"CWE-200",
52+
"CWE-522",
53+
"CWE-862"
54+
],
55+
"severity": "HIGH",
56+
"github_reviewed": true,
57+
"github_reviewed_at": "2026-04-16T21:44:49Z",
58+
"nvd_published_at": null
59+
}
60+
}

0 commit comments

Comments
 (0)