CVE-2026-54596 ITFlow: Authenticated SQL Injection via recurring_invoice_frequency Parameter Enables Full Database Exfiltration
Authenticated attackers can inject SQL via the recurring invoice frequency parameter to exfiltrate sensitive data and potentially take over administrative accounts.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-54596?
CVE-2026-54596 is a high-severity SQL injection vulnerability in itflow-org itflow, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
ITFlow provides an IT documentation, ticketing and accounting system for small managed service providers. Prior to version 26.07, an authenticated Technician or higher with access to at least one client invoice can inject SQL through the frequency parameter handled by agent/post/recurring_invoice.php. The handler passes recurring_invoice_frequency through sanitizeInput but interpolates it unquoted into DATE_ADD, allowing SQL syntax to escape the interval expression, assign additional INSERT columns, store subquery results in recurring_invoice_note, and expose those results through agent/recurring_invoice.php. The persisted recurring_invoice_frequency can execute again when Force Recurring uses it in a later UPDATE, allowing another legitimate user to trigger the second-order injection. This can expose password hashes, SMTP credentials, user records, and database metadata, modify database fields, and enable administrative takeover after credential cracking. This issue is fixed in version 26.07.
Weakness: CWE-89
Which versions are affected by CVE-2026-54596?
How do I fix CVE-2026-54596?
No fix has been published for CVE-2026-54596 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-54596 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54596 exists.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-f9m3-qjc9-v27j.