CVE-2025-29189 json
Flowise Vulnerable to SQL Injection via `tableName` Parameter
published 2025-04-09 19 mo ago modified 2026-10-05 34 d ago also GHSA-gjx9-wg9x-7gvp , EUVD-2025-10669
- cvss
- 7.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Flowise <= 2.2.3 is vulnerable to SQL Injection. via tableName parameter at Postgres_VectorStores.
Patch / fix
- npm flowise-components 2.2.4
- github.com/FlowiseAI/Flowise@9a417bd commit
- github.com/FlowiseAI/Flowise#3818 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- drive.google.com https://drive.google.com/file/d/1WHPslTmQmAM9xPJifULS2qAo7hcidB4L/view?usp=sharing referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| CNA | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | flowise-components | <2.2.4 |
2.2.4 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/FlowiseAI/Flowise/pull/3818
web
-
github.com
/FlowiseAI/Flowise/commit/9a417bdc95f58d6dd92cbf60dad42414aba34754
web
-
drive.google.com
/file/d/1WHPslTmQmAM9xPJifULS2qAo7hcidB4L/view?usp=sharing
exploit, web, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-29189
advisory
-
github.com
/FlowiseAI/Flowise
package
Sources
- CVE List CVE-2025-29189
- GitHub Advisory GHSA-gjx9-wg9x-7gvp
- NVD CVE-2025-29189
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.