CVE-2026-96429: Flowring Agentflow 4.0 SQL Injection

CVE-2026-96429 is a SQL injection vulnerability in Flowring Agentflow 4.0 affecting the /WebAgenda/SMBAjaxConfigProcess.do endpoint. Attackers can execute arbitrary SQL commands through the id parameter. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

CVE-2026-96429 Overview

CVE-2026-96429 is a SQL Injection vulnerability [CWE-89] affecting Flowring Agentflow 4.0 versions released before 2025/08/08. The flaw resides in the /WebAgenda/SMBAjaxConfigProcess.do API endpoint, where the id parameter is passed to a database query without proper sanitization. Remote, unauthenticated attackers can execute arbitrary SQL commands against the backing database.

Critical Impact
Unauthenticated attackers can read, modify, or delete sensitive data stored in the Agentflow database, and may leverage database features to pivot deeper into the enterprise workflow environment.

Affected Products

Flowring Agentflow 4.0 versions released before 2025/08/08
The /WebAgenda/SMBAjaxConfigProcess.do API endpoint
Deployments exposing the WebAgenda module to untrusted networks

Discovery Timeline

2026-09-29 - CVE-2026-96429 published to the National Vulnerability Database (NVD)
2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-96429

Vulnerability Analysis

The vulnerability exists in the SMBAjaxConfigProcess.do handler within the WebAgenda module of Flowring Agentflow 4.0. The endpoint accepts an id parameter over HTTP and incorporates the value directly into a SQL statement. Because the input is not parameterized or validated, an attacker can append additional SQL syntax to change the meaning of the query.

Successful exploitation yields the same privileges as the database account used by the application. Attackers can enumerate tables, extract credentials, alter workflow configurations, or execute stored procedures depending on the database engine in use. The endpoint requires no authentication, so exploitation can occur across any network path that reaches the WebAgenda service.

Root Cause

The root cause is improper neutralization of special elements in a SQL command [CWE-89]. The id parameter is concatenated into a query string rather than bound as a parameter through a prepared statement. Any client-supplied value containing SQL metacharacters is interpreted by the database engine.

Attack Vector

Exploitation requires only network access to the /WebAgenda/SMBAjaxConfigProcess.do endpoint. An attacker sends a crafted HTTP request in which the id parameter carries a SQL payload. Common techniques against this class of flaw include UNION-based extraction, boolean and time-based blind injection, and stacked queries where the database driver permits them. Refer to the Zuso AI CVE Advisory for vendor-published technical details.

Detection Methods for CVE-2026-96429

Indicators of Compromise

HTTP requests to /WebAgenda/SMBAjaxConfigProcess.do containing SQL metacharacters such as single quotes, UNION SELECT, --, /*, or WAITFOR DELAY in the id parameter.
Unexpected database errors or long-running queries originating from the Agentflow application account.
New or modified rows in Agentflow configuration tables that do not correlate with administrative activity.

Detection Strategies

Deploy Web Application Firewall (WAF) signatures that inspect the id parameter for SQL injection payloads on the WebAgenda endpoint.
Enable database query logging and alert on syntactically anomalous statements from the Agentflow service account.
Correlate web server access logs with database audit logs to identify request-to-query patterns consistent with injection attempts.

Monitoring Recommendations

Baseline normal traffic to SMBAjaxConfigProcess.do and alert on volumetric spikes or requests from unexpected source addresses.
Monitor outbound connections from the Agentflow host that may indicate data exfiltration following successful injection.
Track authentication failures and privilege changes on the backing database to detect post-exploitation activity.

How to Mitigate CVE-2026-96429

Immediate Actions Required

Upgrade Flowring Agentflow 4.0 to a build dated 2025/08/08 or later that remediates the SQL injection.
Restrict network access to the WebAgenda endpoint so that only trusted management networks can reach /WebAgenda/SMBAjaxConfigProcess.do.
Rotate database credentials used by the Agentflow application if exploitation is suspected.

Patch Information

Flowring addressed the vulnerability in Agentflow 4.0 builds released on or after 2025/08/08. Consult the Zuso AI CVE Advisory for the vendor's remediation details and confirm the fixed build with Flowring before deployment.

Workarounds

Block or filter requests to /WebAgenda/SMBAjaxConfigProcess.do at the reverse proxy or WAF until the patched build is installed.
Enforce least-privilege on the database account used by Agentflow so that a successful injection cannot alter schemas or invoke administrative procedures.
Disable the WebAgenda module on hosts that do not require it.

bash

# Example WAF rule to block SQL metacharacters in the vulnerable parameter
# (adapt syntax to your WAF vendor before deployment)
SecRule REQUEST_URI "@contains /WebAgenda/SMBAjaxConfigProcess.do" \
  "chain,deny,status:403,id:1026964290,msg:'CVE-2026-96429 SQLi attempt'"
  SecRule ARGS:id "@rx (?i)(union(\s|/\*.*\*/)+select|--|;|/\*|xp_|waitfor\s+delay|sleep\s*\()" "t:none"