CVE-2024-31621 is a high-severity (CVSS 7.6) Code Injection vulnerability in flowise. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for flowise — see the affected versions and patch details below.
Flowise vulnerable to code injection via api/v1
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-31621.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
flowisenpmDescription
An issue in FlowiseAI Inc Flowise v.1.6.2 and before allows a remote attacker to execute arbitrary code via a crafted script to the api/v1 component.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | all versions | 1.8.1npm install flowise@1.8.1 |
Affected Products
flowiseflowiseaiResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Flowise 1.6.5 - Authentication Bypass
by Maerifat Majeed · Apr 21, 2024
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flowise to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-31621 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
How to detect CVE-2024-31621
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2024-31621 -u https://target- Template
- Flowise 1.6.5 - Authentication Bypass
- Severity
- high
- Impact
- Attackers can bypass authentication and gain unauthorized access to the Flowise application and its data.
- Remediation
- Update Flowise to version 1.6.6 or later.
Template by ProjectDiscovery nuclei-templates (DhiyaneshDK), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2024-31621 in your dependencies?
Find it across npm, including transitive dependencies.