Security readout for executives and security teams
Plain-English summary
Flowise through 2.2.7 is reported vulnerable to SQL injection in an authenticated import API. A user with access to import chatflows could manipulate an imported chatflow ID and potentially read sensitive database data, including credentials. This is a high business risk where Flowise is used to store secrets or connect AI workflows to internal systems.
Executive priority
Treat this as urgent for any Flowise instance storing production credentials or integrating with sensitive systems. It is not currently reported as actively exploited in the bundle, but the potential credential exposure makes delay risky.
Technical view
The issue is CWE-89 in Flowise importChatflows. The chatflow.id value from a JSON import is insufficiently validated and concatenated into a SQL IN clause, enabling arbitrary SQL execution. The bundle specifically notes blind and error-based extraction from the credential table. CVSS v4.0 is 8.5 with PR:H and no user interaction.
Likely exposure
Exposure is limited to Flowise deployments where authenticated users can access the importChatflows API. The bundle says Flowise through 2.2.7, but the affected-version metadata is incomplete or inconsistent, so teams should verify against vendor advisory data.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation evidence. Exploitation requires authenticated access with high privileges per the CVSS vector, but successful abuse could expose stored credentials and other database contents.
Researcher notes
The source bundle identifies the vulnerable sink as chatflow.id during JSON import into importChatflows and describes unsanitized SQL IN clause construction. Avoid assuming unauthenticated exploitability: CVSS lists PR:H. Version data should be verified because the structured affected field conflicts with the prose description.
Mitigation direction
- Review the Flowise GitHub advisory for confirmed fixed versions and upgrade guidance.
- Inventory Flowise deployments and flag versions through 2.2.7 for urgent review.
- Restrict chatflow import capability to trusted administrators while remediation is assessed.
- Rotate Flowise-stored credentials if compromise or suspicious import activity is found.
- Monitor vendor and VulnCheck advisories for patch, workaround, and detection updates.
Validation and detection
- Confirm whether Flowise is deployed and record exact versions.
- Verify who can access the importChatflows API in each environment.
- Review logs for recent chatflow imports, SQL errors, or unusual authenticated activity.
- Check whether credentials stored in Flowise could grant access to sensitive systems.
- Validate remediation against the vendor advisory before closing the finding.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-71332 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N1.25.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.5HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-9c4c-g95m-c8cp)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - SQL Injection in importChatflows API via chatflow.id ParameterCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.