External risk intelligence

Flowring Agentflow SQL Injection in SMBAjaxAutoComplete API Endpoint

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-96428

The vulnerability exists in an API endpoint (/WebAgenda/SMBAjaxAutoComplete.do) within a workflow management system. Such web applications and their associated API endpoints are commonly deployed as internet-facing services to facilitate remote access and external integration in typical enterprise environments.

SQL Injection

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A SQL injection vulnerability exists in a Flowring Agentflow API, potentially allowing remote attackers to execute arbitrary SQL commands. The main concern is confirming whether this specific technology is in use and exposed.

Unauthenticated attackers can inject malicious commands.
Understand the technology's presence and exposure.
Assess potential for unauthorized data access or modification.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending a specially crafted request to the `/WebAgenda/SMBAjaxAutoComplete.do` API. This would allow them to inject malicious SQL commands, potentially leading to unauthorized access and modification of sensitive data.

Requires no authentication or user interaction.
Triggered by sending a malicious request to an API endpoint.
Risk of arbitrary SQL command execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow remote attackers to execute arbitrary SQL commands, potentially affecting the integrity and availability of the affected system's data.

System data integrity.
Remote SQL command execution.
Service disruption or data corruption.

Operational Fix

Recommended remediation, mitigation, and detection steps

This SQL injection vulnerability in Flowring Agentflow's API endpoint requires immediate attention from the team responsible for the application and its underlying infrastructure. The first step is to identify all instances of this software, determine their exposure, and confirm their business criticality to prioritize remediation efforts.

Application owners must confirm deployment.
Verify external reachability and business impact.
Plan remediation with infrastructure teams.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Flowring Agentflow?

Flowring Agentflow is a business process and workflow management system designed to automate organizational tasks and integrate various enterprise services. It is used to streamline administrative workflows, manage form-based processes, and handle complex data routing within an organization.

What does CWE-89 mean for CVE-2026-96428?

CWE-89 identifies this vulnerability as an SQL Injection. In plain terms, it means the application does not properly sanitize input provided by a user. Because of this, an attacker can insert their own database commands into the software, effectively tricking it into running unauthorized queries against the back-end system.

How can an attacker trigger this vulnerability?

An attacker can exploit this by sending a specially crafted web request to the /WebAgenda/SMBAjaxAutoComplete.do API endpoint. Specifically, the attack occurs through the 'words' parameter. The vulnerability is not triggered by standard, legitimate use of the application; it requires the submission of malicious SQL commands instead of expected input.

Do I need to worry if my instance is not internet-facing?

According to Halo Surface Signal, this software is commonly deployed as an internet-facing service. However, if your instance is strictly internal, the risk profile changes significantly because attackers would generally need prior access to your internal network to reach the affected API endpoint.

When should I take action for this CVE?

You should prioritize this immediately if you use Flowring Agentflow. Your first step is to inventory all installations of this software across your environment. Once identified, verify if those specific instances are reachable from the network and determine if they are running the affected versions to plan your remediation steps.

References

zuso.ai/cve-advisory/advisory

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.