dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-59920

HIGH · 8.6 CVSS v4.0 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

time@work 7.0.5 contains an authenticated blind SQL injection vulnerability in the IDClient parameter of a project display query. When exploited with a TWAdmin user having sysadmin privileges, the vulnerability enables OS command execution via database stored procedures; otherwise it allows unauthorized database data exfiltration.

MitigationImplement parameterized queries or prepared statements for the IDClient parameter, apply least-privilege principles to database accounts (disable xp_cmdshell and similar procedures for non-admin users), and validate all user-supplied input before database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify time@work version
    Locate the installed time@work application and retrieve its version number. Check installation directories, about pages, or version files. Compare the installed version against 7.0.5.
    Affected if The installed version is 7.0.5 exactly, or falls within the 7.0.5 release line (e.g., 7.0.5.x).
  2. Confirm authentication is in use
    Verify that the time@work application requires authentication for access, particularly for the project display functionality where the IDClient parameter is processed.
    Affected if The application accepts authenticated requests and the TWAdmin user account exists with access to the project display query endpoint.
  3. Check database user privileges
    Examine the database account used by time@work for queries. Determine if this account has been granted the sysadmin server role or elevated privileges on the SQL Server instance.
    Affected if The application database account possesses sysadmin privileges, enabling OS command execution via stored procedures like xp_cmdshell when exploited.
  4. Identify IDClient parameter exposure
    Inspect the project display query functionality in the application. Determine if the IDClient parameter is used in SQL queries without parameterized query handling.
    Affected if The project display query accepts and processes the IDClient parameter in a way that allows SQL injection (non-parameterized query construction).

You are affected if time@work 7.0.5 is installed, the application uses authentication with a TWAdmin account, and the IDClient parameter in the project display query handles user input without parameterized queries, with sysadmin privileges on the database user enabling the full OS command execution impact.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements for the IDClient parameter, apply least-privilege principles to database accounts (disable xp_cmdshell and similar procedures for non-admin users), and validate all user-supplied input before database queries.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
34.0 hours of engineering $6,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59920 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59920 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data