# CVE-2024-36423: GHSL-2023-246: Flowise xss in /api/v1/public-chatflows/id > Attackers can inject JavaScript via crafted URLs in Flowise public chatflows, potentially stealing user data or hijacking sessions. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 1 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-fccx-2pwj-hrq7 ## What is CVE-2024-36423? CVE-2024-36423 is a medium-severity cross-site scripting vulnerability in Flowiseai Flowise, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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/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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2024-36423? 2 open source packages ship an affected version, including flowise. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `flowise` | npm | All versions to 1.4.3 | None | | `flowise` | npm | All versions to 1.4.3 | None | Products: Flowiseai Flowise. ## How do I fix CVE-2024-36423? No fix has been published for CVE-2024-36423 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-36423 being exploited? There is no known exploitation of CVE-2024-36423 in the wild and no public exploit code. ## Other vulnerabilities in Flowiseai Flowise - [CVE-2025-71338](https://insights.sbomify.com/CVE-2025-71338/): Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API (critical 10.0) - [CVE-2026-40933](https://insights.sbomify.com/CVE-2026-40933/): Flowise: Authenticated RCE Via MCP Adapters (critical 10.0) - [CVE-2025-61913](https://insights.sbomify.com/CVE-2025-61913/): Flowise is vulnerable to arbitrary file read, arbitrary file write (critical 10.0) - [CVE-2025-59528](https://insights.sbomify.com/CVE-2025-59528/): Flowise has Remote Code Execution vulnerability (critical 10.0) - [CVE-2026-52098](https://insights.sbomify.com/CVE-2026-52098/): Code injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-36423 and fix it if it is affected. What it is: CVE-2024-36423 is a medium-severity cross-site scripting vulnerability in Flowiseai Flowise, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-36423 in the wild and no public exploit code. Affected packages and fixed versions: - flowise (npm): affected all versions up to 1.4.3; no fix listed - flowise (npm): affected all versions up to 1.4.3; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-36423/ (Markdown: https://insights.sbomify.com/CVE-2024-36423/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-36423 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-36423 - OSV: https://osv.dev/vulnerability/CVE-2024-36423 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-36423/ Summaries are generated and may contain mistakes; the official description above is the record.