Skip to main content
CVE-2025-15560VulnerabilityPublished Updated

CVE-2025-15560: NesterSoft WorkTime (on-prem/cloud) · SQL Injection

Affects NesterSoft WorkTime (on-prem/cloud)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NesterSoft Inc.WorkTime (on-prem/cloud)Affected
  • <=11.8.8
Fixed in–

AI-suggested

To mitigate CVE-2025-15560, organizations should immediately identify all instances of WorkTime running versions 11.8.8 or earlier and prioritize upgrading to a patched version once released by NesterSoft Inc. In the absence of an official patch, organizations should implement the following specific measures: 1) Restrict access to the WorkTime widget API endpoint to only trusted and necessary users and systems, employing network segmentation and firewall rules to limit exposure. 2) Enforce strong authentication and monitor for unusual login patterns to detect potential misuse of low-privilege accounts. 3) Conduct thorough input validation and sanitization on all API inputs at the application layer, if possible via custom WAF (Web Application Firewall) rules tailored to detect and block SQL injection patterns targeting the widget API. 4) Enable detailed logging and real-time alerting on database queries and API calls to identify suspicious activity indicative of SQL injection attempts. 5) Consider deploying database activity monitoring tools that can detect anomalous SQL commands and block unauthorized queries. 6) Review and minimize database user privileges associated with the WorkTime application to limit the potential damage from exploited SQL injection. 7) Regularly back up databases and verify restore procedures to ensure recovery in case of data corruption or deletion. These targeted mitigations, combined with timely patching, will significantly reduce the risk posed by this vulnerability.

Description

An authenticated attacker with minimal permissions can exploit a SQL injection in the WorkTime server "widget" API endpoint to inject SQL queries. If the Firebird backend is used, attackers are able to retrieve all data from the database backend. If the MSSQL backend is used the attacker can execute arbitrary SQL statements on the database backend and gain access to sensitive data.

References

Community reviews

Loading reviews…