CVE-2024-36423: Flowise Cross-site Scripting in /api/v1/public-chatflows/id
Flowise 1.4.3 reflects the chatflow ID unescaped in the 404 page of `GET /api/v1/public-chatflows/:id`. A crafted link runs attacker JavaScript in the browser of whoever opens it. GitHub Security Lab tracks it as GHSL-2023-246. No patched version exists for the `flowise` package.
Published Aug 5, 2024 · Analysis Nov 1, 2026
What an attacker can do
The public-chatflows route is the one the embedded chat widget uses to load a published flow, so it is meant to be reachable without a login. When the ID matches no flow, the handler calls res.status(404).send with the raw req.params.id inside the text. The response is text/html, so markup in the ID becomes live script.
An attacker needs only a victim who clicks a link to the Flowise host. The script then runs with the Flowise origin. It can steal what the page can reach, draw fake dialogs or redirect the user. The advisory also says the XSS can be combined with the file path injection in /api/v1/openai-assistants-file, which lets an attacker with no direct access to Flowise read files from the server through the victim's browser. The same unescaped pattern exists in sibling routes such as /api/v1/flow-config/:id, so fixing one route alone leaves others open.
Who is affected
Flowise 1.4.3 was tested, and the advisory data lists <= 1.4.3 for the npm package flowise. The default unauthenticated setup is the worst case. Check the installed version:
npm ls flowiseFor container deployments, read the image tag. The sources did not test later versions, so confirm yours directly.
flowise
- Ecosystem
- npm
- Affected
- <= 1.4.3
- Fixed in
- No patched version yet
- Check
npm ls flowise
How to fix it
There is no patched version in the advisory data. The maintainers acknowledged the reports in December 2023 and then went quiet, according to the researchers' write-up. The recommended code fix is to encode or avoid echoing request data in responses.
Until a release lands, restrict who can reach the server: enable Flowise authentication, keep it off the open internet, and use a reverse proxy rule to refuse public-chatflows paths that contain anything but a UUID. These are operator mitigations, not vendor guidance. Watch the project's releases for a fix.
How to tell if you were hit
Look in access logs for GET requests to /api/v1/public-chatflows/ where the final segment contains <, %3C, script, onerror or javascript:. These requests return 404. Compare them against the UUIDs your widgets really use. Pair this with a search for .. in fileName on /api/v1/openai-assistants-file, because the two flaws can be chained.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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/public-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.
Questions
- How is CVE-2024-36423 different from CVE-2024-36422?
Same bug class and same 1.4.3 code, but another route. This one is
/api/v1/public-chatflows/:id; CVE-2024-36422 is/api/v1/chatflows/:id. Each route needs its own fix and its own log search.- Does the attacker need a Flowise account?
No, not in the default configuration, which has no authentication. The victim must open the crafted link, so the CVSS vector sets user interaction to required.
- Is there a fixed Flowise version?
The advisory lists none. The maintainers did not respond to the researchers after acknowledging the report. Apply the access limits above and watch for a release.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More Flowise vulnerabilities
All Flowise entriesCVE-2026-73483
Flowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromium
critical9.4Oct 7, 2026CVE-2026-73487
Flowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypass
critical9.0Oct 7, 2026CVE-2026-69250
Flowise: Unauthenticated OAuth2 Refresh Enables Non-Blind SSRF and Secret Exfiltration
high8.5Aug 4, 2026CVE-2026-69251
Flowise RCE via TypeORM DataSource
critical9.0Aug 4, 2026CVE-2026-69252
Flowise: Missing authorization on `/api/v1/files` allows low-privileged API keys to list and delete files across workspaces within the same organization
high7.2Aug 4, 2026CVE-2026-69253
Flowise Sandbox Escape to RCE
critical9.0Aug 4, 2026
