{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54596 exists.","fix":"No fix has been published for CVE-2026-54596 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-54596 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54596 exists.\n\nAffected product: itflow-org itflow. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54596/ (Markdown: https://insights.sbomify.com/CVE-2026-54596/index.md)","id":"CVE-2026-54596","markdown":"https://insights.sbomify.com/CVE-2026-54596/index.md","name":"CVE-2026-54596","record":{"aliases":["GHSA-f9m3-qjc9-v27j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IT documentation system","requires_auth":"low_privilege","summary":"Authenticated attackers can inject SQL via the recurring invoice frequency parameter to exfiltrate sensitive data and potentially take over administrative accounts.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-15","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-15T22:09:02Z","kind":"github_poc","ref":"https://github.com/iltosec/CVE-2026-54596","stars":0,"title":"CVE-2026-54596 - Authenticated SQL Injection via recurring_invoice_frequency Parameter Enables Full Database Exfiltration"}],"tier":"weaponised"},"has_fix":false,"headline":"ITFlow: Authenticated SQL Injection via recurring_invoice_frequency Parameter Enables Full Database Exfiltration","id":"CVE-2026-54596","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ITFlow: Authenticated Time-Based Blind SQL Injection in ITFlow via expires Parameter","id":"CVE-2026-54597"},"packages":[],"prev":{"headline":"OmniBlocks: Spamming in Discussions tab possible via disc.yml","id":"CVE-2026-54594"},"products":["itflow"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["itflow-org"]},"summary":"Authenticated attackers can inject SQL via the recurring invoice frequency parameter to exfiltrate sensitive data and potentially take over administrative accounts.","url":"https://insights.sbomify.com/CVE-2026-54596/"}