https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T11:54:51.536384+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-52822 fkie_cve-2026-52822 2026-09-29T11:54:54.935332+00:00

Kimai is an open-source time tracking application. Prior to 2.58.0, PATCH /api/timesheets/{id}/restart, PATCH /api/timesheets/{id}/duplicate, and the web duplicate workflow can derive a new record from an owned historical timesheet after the user's access to its project or activity has been revoked. TimesheetVoter evaluates the own-timesheet permission before current team access, and its canStart() logic validates object visibility but does not verify the user's current team access to the referenced project and activity. An old entry therefore acts as a persistent capability to create new time records under an unauthorized project and activity, corrupting budgets, statistics, reports, and invoices after an administrative revocation. This issue is fixed in version 2.58.0.

 https://vulnerability.circl.lu/vuln/ghsa-c6w6-57jj-62vh GHSA-c6w6-57jj-62vh — Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation 2026-09-29T11:54:54.935538+00:00

Affected: Packagist: kimai/kimai

### Summary

Kimai 2.56.0 contains an authenticated authorization bypass in the timesheet `restart` and `duplicate` workflows. After a user loses access to a project, the user can still derive a new timesheet from one of their historical entries and create a new record under that now-unauthorized project and activity combination.

This is a permission revocation bypass with persistent write impact. The issue affects both `restart` and `duplicate`, which trust ownership of an old timesheet more than the user's current access to the underlying project, activity, and customer.

### Details

The issue affects the following operations:

- `PATCH /api/timesheets/{id}/restart` - `PATCH /api/timesheets/{id}/duplicate`

The root cause is that authorization gives too much weight to the fact that the original timesheet belongs to the current user. In `src/Voter/TimesheetVoter.php`, the `*_own_timesheet` branch is evaluated before team-based access checks.

The restart/duplicate capability check also verifies only object visibility, not whether the current user still has team-based access to the referenced objects.

In `src/API/TimesheetController.php`, the restart flow copies the historical `project` and `activity` into a new candidate timesheet.

The duplicate flow similarly clones the historical record and saves it.

In `src/Timesheet/TimesheetService.php`, creation of a new running entry still relies on `isGranted('start', $timesheet)`.

For historical entries that belong to the cu…