CVE-2026-54596: ITFlow: Authenticated SQL Injection via recurring_invoice_frequency Parameter Enables Full Database Exfiltration

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-17).

Weakness: CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)

How it can be exploited

Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 4 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS
0.005
low predicted chance of attack
VEDAS
0.987
strong exploit evidence
On CISA KEV
Not listed
Detection rule
Suricata

Who is affected

ProductAffectedNot affected
itflow-org itflowversion < 26.07Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-54596 ITFlow - SQL Injection via recurring invoice frequency parameter. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-54596 ITFlow - SQL Injection via recurring invoice frequency parameter"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/recurring_invoice.php"; nocase; fast_pattern; http.request_body; content:"frequency"; nocase; pcre:"/(?:\x27|%27|\bunion\b|\bselect\b|\bsleep\x28|\bupdatexml\x28|\bextractvalue\x28|information_schema|date_add\x28)/i"; classtype:web-application-attack; reference:cve,CVE-2026-54596; reference:url,https://www.exploit.observer/?keyword=CVE-2026-54596&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=itflow&match=exact; sid:1095407; rev:1;)

CVE-2026-54596.rules on GitHub

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners

Feasible SecurityAskealGoTrust