Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-96429 – SQL Injection – Flowring Agentflow 4.0 (before 2025/08/08)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-96429 is a critical SQL injection vulnerability in Flowring Technology Corp’s Agentflow 4.0 platform. The flaw resides in the /WebAgenda/SMBAjaxConfigProcess.do API endpoint, where the id parameter is passed into a SQL query without proper sanitization, allowing remote attackers to execute arbitrary SQL commands. The vulnerability carries a CVSS v4.0 base score of 9.3 (Critical) and is remotely exploitable over the network with no authentication or user interaction required.

Technical details

  • Root cause: The id parameter supplied to the /WebAgenda/SMBAjaxConfigProcess.do endpoint is concatenated into a backend SQL query without adequate input validation or parameterization (CWE-89: Improper Neutralization of Special Elements used in an SQL Command).
  • Trigger condition: An attacker sends a crafted HTTP request to the vulnerable endpoint with a malicious payload in the id parameter.
  • Attack vector: Network-based; the vector string (AV:N/AC:L/AT:N/PR:N/UI:N) indicates the attack requires no privileges, no user interaction, and no special attack complexity or conditions.
  • Impact: Successful exploitation allows arbitrary SQL command execution, which can result in full compromise of confidentiality, integrity, and availability of the backend database (VC:H/VI:H/VA:H), potentially exposing or corrupting sensitive data and enabling further compromise of the affected system.

Affected software

  • Flowring Technology Corp Agentflow 4.0 — all versions released before 2025/08/08

Severity

  • CVSS v4.0 Base Score: 9.3 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Agentflow 4.0 to a build released on or after 2025/08/08, which addresses this issue. Confirm with Flowring Technology Corp that the applied build/patch level supersedes the vulnerable date noted in the CVE record.
  • If no patch is available: Restrict network exposure of the /WebAgenda/ application path to trusted internal networks only; deploy a web application firewall (WAF) rule to block anomalous or SQL-metacharacter-laden input to the id parameter on the SMBAjaxConfigProcess.do endpoint; monitor application and database logs for suspicious query patterns targeting this endpoint.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge