Flowise up to 2.2.7 importChatflows API chatflow.id sql injection

Summaryinfo

A vulnerability categorized as critical has been discovered in Flowise up to 2.2.7. Affected by this issue is some unknown functionality of the file chatflow.id of the component importChatflows API. Such manipulation of the argument chatflow.id leads to sql injection. This vulnerability is referenced as CVE-2025-71332. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability was found in Flowise up to 2.2.7. It has been rated as critical. Affected by this issue is an unknown functionality of the file chatflow.id of the component importChatflows API. The manipulation of the argument chatflow.id with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Flowise through 2.2.7 contains a SQL injection vulnerability in the importChatflows API. Due to insufficient validation of the chatflow.id value, an authenticated user can supply a crafted JSON import file whose id field is concatenated unsanitized into a SQL IN clause, allowing arbitrary SQL to be executed, including blind and error-based extraction of data from the credential table.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-71332 since 06/20/2026. The exploitation is known to be easy. The attack may be launched remotely. The exploitation requires an enhanced level of successful authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/24/2026). The MITRE ATT&CK project declares the attack technique as T1505.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Flowise

Version

• 2.2.0
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.2.5
• 2.2.6
• 2.2.7

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion