CVE-2025-15561

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-02-19. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An attacker can exploit the update behavior of the WorkTime monitoring daemon to elevate privileges on the local system to NT Authority\SYSTEM. A malicious executable must be named  WTWatch.exe and dropped in the C:\ProgramData\wta\ClientExe directory, which is writable by "Everyone". The executable will then be run by the WorkTime monitoring daemon.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

February 19, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available.
generic Patch Available🟡 PoC Available

Multiple Critical Vulnerabilities in NesterSoft WorkTime (on-prem/cloud) - SEC Consult

https://r.sec-consult.com/worktime

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-22 14:47 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:06 UTCEPSS rescore
  4. 2026-09-16 05:13 UTCEPSS rescore
  5. 2026-09-15 03:08 UTCEPSS rescore
  6. 2026-09-13 16:45 UTCEPSS rescore
  7. 2026-09-12 14:59 UTCEPSS rescore
  8. 2026-09-11 14:51 UTCEPSS rescore
  9. 2026-09-11 09:35 UTCEPSS rescore
  10. 2026-09-10 09:33 UTCEPSS rescore
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-06 13:46 UTCEPSS rescore
  13. 2026-09-04 13:59 UTCEPSS rescore
  14. 2026-09-04 05:05 UTCEPSS rescore
  15. 2026-09-02 14:10 UTCEPSS rescore
  16. 2026-09-01 13:52 UTCEPSS rescore
  17. 2026-09-01 04:38 UTCEPSS rescore
  18. 2026-08-30 19:16 UTCEPSS rescore
  19. 2026-08-30 01:21 UTCEPSS rescore
  20. 2026-08-28 21:40 UTCEPSS rescore
  21. 2026-08-27 14:24 UTCEPSS rescore
  22. 2026-08-26 14:45 UTCEPSS rescore
  23. 2026-08-24 14:15 UTCEPSS rescore
  24. 2026-08-21 23:48 UTCEPSS rescore
  25. 2026-08-20 22:54 UTCEPSS rescore
Show 44 more
  1. 2026-08-19 17:02 UTCEPSS rescore
  2. 2026-08-17 13:46 UTCEPSS rescore
  3. 2026-08-16 14:55 UTCEPSS rescore
  4. 2026-08-16 02:13 UTCEPSS rescore
  5. 2026-08-16 02:13 UTCEPSS rescore
  6. 2026-08-15 01:29 UTCEPSS rescore
  7. 2026-08-14 21:49 UTCGHSA enrichment
  8. 2026-08-14 09:36 UTCEG score recompute
  9. 2026-08-14 09:36 UTCGHSA enrichment
  10. 2026-08-13 21:59 UTCEPSS rescore
  11. 2026-08-13 01:47 UTCEG score recompute
  12. 2026-08-13 01:47 UTCGHSA enrichment
  13. 2026-08-12 13:49 UTCEPSS rescore
  14. 2026-08-12 02:08 UTCEG score recompute
  15. 2026-08-12 02:08 UTCGHSA enrichment
  16. 2026-08-11 13:41 UTCEPSS rescore
  17. 2026-08-11 07:11 UTCEG score recompute
  18. 2026-08-11 07:11 UTCGHSA enrichment
  19. 2026-08-10 23:59 UTCEPSS rescore
  20. 2026-08-10 09:33 UTCGHSA enrichment
  21. 2026-08-09 20:57 UTCEG score recompute
  22. 2026-08-09 20:57 UTCGHSA enrichment
  23. 2026-08-09 13:45 UTCEPSS rescore
  24. 2026-08-09 09:11 UTCEG score recompute
  25. 2026-08-09 09:11 UTCGHSA enrichment
  26. 2026-08-08 09:12 UTCGHSA enrichment
  27. 2026-08-07 21:27 UTCEG score recompute
  28. 2026-08-07 21:27 UTCGHSA enrichment
  29. 2026-08-07 16:26 UTCEPSS rescore
  30. 2026-08-06 13:45 UTCEPSS rescore
  31. 2026-08-06 03:27 UTCEG score recompute
  32. 2026-08-06 03:27 UTCGHSA enrichment
  33. 2026-08-05 19:16 UTCEPSS rescore
  34. 2026-08-04 15:09 UTCEPSS rescore
  35. 2026-08-03 10:35 UTCEPSS rescore
  36. 2026-08-02 20:09 UTCEG score recompute
  37. 2026-08-02 20:09 UTCGHSA enrichment
  38. 2026-08-01 04:14 UTCEPSS rescore
  39. 2026-07-30 16:26 UTCEPSS rescore
  40. 2026-07-30 01:29 UTCEPSS rescore
  41. 2026-07-28 15:35 UTCEPSS rescore
  42. 2026-07-27 14:12 UTCEPSS rescore
  43. 2026-07-27 13:27 UTCEG score recompute
  44. 2026-07-27 13:26 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-15561?
CVE-2025-15561 is a high vulnerability published on February 19, 2026. An attacker can exploit the update behavior of the WorkTime monitoring daemon to elevate privileges on the local system to NT Authority\SYSTEM. A malicious executable must be named WTWatch.exe and dropped in the C:\ProgramData\wta\ClientExe directory, which is writable by "Everyone". The executable…
When was CVE-2025-15561 disclosed?
CVE-2025-15561 was first published in the National Vulnerability Database on February 19, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15561 actively exploited?
CVE-2025-15561 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2025-15561?
CVE-2025-15561 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-15561?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15561, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-15561

Explore →

Is Your Infrastructure Affected by CVE-2025-15561?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs