Overview
CVE-2025-29189 is a severe SQL Injection vulnerability affecting Flowise versions up to and including 2.2.3. This flaw opens the gate for potential system compromise and data leakage, making it a significant concern for all organizations utilizing this software. Given the CVSS Severity Score of 7.6, immediate attention and remediation are advised.
Vulnerability Summary
CVE ID: CVE-2025-29189
Severity: Critical (7.6 CVSS Score)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
Flowise | <= 2.2.3 How the Exploit Works
The vulnerability stems from the inappropriate handling of the ‘tableName’ parameter in Postgres_VectorStores within Flowise. An attacker can manipulate this parameter to inject malicious SQL commands. These commands are then executed by the database, leading to unauthorized access, data corruption, or even full system takeover.
Conceptual Example Code
Below is a conceptual example of how this vulnerability might be exploited.
POST /Postgres_VectorStores HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
tableName=users; DROP TABLE users; --
In this example, the attacker sends a POST request with a malicious payload. The ‘tableName’ parameter is exploited to drop the ‘users’ table, resulting in potential data loss.
Mitigation Guidance
Organizations are advised to apply the patch provided by the vendor immediately. In cases where immediate patching is not possible, implementation of a Web Application Firewall (WAF) or Intrusion Detection System (IDS) may serve as a temporary mitigation strategy, helping to prevent the exploitation of this vulnerability in the interim.
