CVE-2026-52823: Kimai · Login CSRF in the Timesheet Stop and Restart API Endpoints Allows Unauthorized State Changes
Affects kimai/kimaiSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.58.0 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.58.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
Upgrade kimai/kimai to 2.58.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagistkimai/kimai | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is addressed by removing the GET routes for stop and restart operations and allowing these actions only via PATCH requests. Users should upgrade to Kimai version 2.58.0 or later where this fix is implemented. No additional mitigations are specified by the vendor advisory.
Description
Kimai 2.56.0 and earlier versions contain an authenticated cross-site request forgery (CSRF) vulnerability in the timesheet stop and restart API endpoints. The application exposes state-changing operations via GET requests, which should be read-only, allowing attackers to trick logged-in users into triggering unauthorized timesheet state changes. This can stop running timesheets or restart historical ones without user consent, potentially corrupting time tracking data and affecting billing or auditing processes. The issue is fixed by removing the GET routes and limiting these operations to PATCH requests only.