Ameeba Exploit Tracker

Tracking CVEs, exploits, and zero-days for defensive cybersecurity research.

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-29189: Critical SQL Injection Vulnerability in Flowise <= 2.2.3

Ameeba Chat Store screens
Download Ameeba Chat

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

Ameeba Chat Icon Escape the Surveillance Era

Most apps won’t tell you the truth.
They’re part of the problem.

Phone numbers. Emails. Profiles. Logs.
It’s all fuel for surveillance.

Ameeba Chat gives you a way out.

  • • No phone number
  • • No email
  • • No personal info
  • • Anonymous aliases
  • • End-to-end encrypted

Chat without a trace.

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.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.
Ameeba Chat