# CVE-2026-54597: ITFlow: Authenticated Time-Based Blind SQL Injection in ITFlow via expires Parameter

> Authenticated users can execute time-based blind SQL injection via the expires parameter to steal sensitive credentials and potentially take over admin accounts.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-m63v-j7fw-hq2h

## What is CVE-2026-54597?

CVE-2026-54597 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 user with module_support write permission and access to a credential record can perform time-based blind SQL injection through the expires parameter of the share_generate_link handler in agent/ajax.php. sanitizeInput applies string-context escaping, but expires is inserted unquoted into the item_expire_at MySQL INTERVAL expression, allowing a crafted expression and interval unit to execute conditional database queries whose results are inferred from response delays. This can expose password hashes, SMTP credentials, API keys, encrypted vault data, and database metadata and support administrative takeover after credential cracking. This issue is fixed in version 26.07.

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

## Which versions are affected by CVE-2026-54597?


## How do I fix CVE-2026-54597?

No fix has been published for CVE-2026-54597 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54597 exists.

Public exploit code:

- CVE-2026-54597 - Authenticated Time-Based Blind SQL Injection in ITFlow (github_poc): https://github.com/iltosec/CVE-2026-54597

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54597 and fix it if it is affected.

What it is: CVE-2026-54597 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54597 exists.

Affected product: itflow-org itflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54597/ (Markdown: https://insights.sbomify.com/CVE-2026-54597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54597
- OSV: https://osv.dev/vulnerability/CVE-2026-54597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54597/
Summaries are generated and may contain mistakes; the official description above is the record.