# CVE-2025-59920: SQL injection in time@work from systems@work

> Authenticated attackers can execute SQL commands via the IDClient parameter, potentially leading to system command execution or data theft.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-whmh-gx62-v47m

## What is CVE-2025-59920?

CVE-2025-59920 is a high-severity SQL injection vulnerability in systems at work time at work, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When hours are entered in time@work, version 7.0.5, it performs a query to display the projects assigned to the user. If the query URL is copied and opened in a new browser window, the ‘IDClient’ parameter is vulnerable to a blind authenticated SQL injection. If the request is made with the TWAdmin user with the sysadmin role enabled, exploiting the vulnerability will allow commands to be executed on the system; if the user does not belong to the sysadmin role, they will still be able to query data from the database.

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

## Which versions are affected by CVE-2025-59920?


## How do I fix CVE-2025-59920?

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

## Is CVE-2025-59920 being exploited?

There is no known exploitation of CVE-2025-59920 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59920 and fix it if it is affected.

What it is: CVE-2025-59920 is a high-severity SQL injection vulnerability in systems at work time at work, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59920 in the wild and no public exploit code.

Affected product: systems at work time at work. 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-2025-59920/ (Markdown: https://insights.sbomify.com/CVE-2025-59920/index.md)
```

## Sources

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

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