CVE-2024-29200: Kimai API returns timesheet entries a user should not be authorized to view
Summary The permission viewothertimesheet performs differently for the Kimai UI and the API, thus returning unexpected data through the API. Details When setting the viewothertimesheet permission to true, on the frontend, users can only see timesheet entries for teams they are a part of.
Published Mar 29, 2024 · Updated Oct 13, 2025
Affected packages
kimai/kimai
- Ecosystem
- Composer (PHP)
- Affected
- < 2.13.0
- Fixed in
- 2.13.0
- Check
composer show kimai/kimai
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The permission view_other_timesheet performs differently for the Kimai UI and the API, thus returning unexpected data through the API.
Details
When setting the view_other_timesheet permission to true, on the frontend, users can only see timesheet entries for teams they are a part of. When requesting all timesheets from the API, however, all timesheet entries are returned, regardless of whether the user shares team permissions or not.
Example: There are projects P1 and P2, Teams T1 and T2, users U1 and U2 and Timesheet entries E1 and E2. U1 is team leader of team T1 and has access to P1. U2 is in Team T2 and has access to both P1 and P2. U2 creates E1 for P1 and E2 for P2. In the UI, U1 with view _other_timesheet perms sees E1 as he is a part of T1 that has access to P1. In the API, however, he has access to E1 and E2.
Additionally, if U1 is not a team leader T1, he does not see any timesheet from a user other than himself in the UI, but still all timesheets in the API.
PoC
- Give a user
view_other_timesheetpermission - The result of the UI and the API call to
/api/timesheets?user=alldiffers in the data that is being returned
Curl command:
curl -X 'GET' \
'https://kimai.instance.com/api/timesheets?user=all' \
-H 'accept: application/json' \
-H 'X-AUTH-USER: username' \
-H 'X-AUTH-TOKEN: api_token'Impact
This is at least an insufficient granularity of access control weakness. People can see timesheet entries they are not supposed to. This greatly affects the confidentiality of timesheet entries.
Restricting API access to administrators is also not a valid solution, as API access is needed, for example, to use the mobile app.
Credited to AstroGD.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-52821
Kimai: Improper Authorization Through Activity Creation with Preset Project Allows Creation Under Unauthorized Projects
medium5.3Jul 14, 2026CVE-2026-52822
Improper Authorization in Kimai Timesheet Restart and Duplicate Allows New Timesheets After Project Access Revocation
medium5.3Jul 14, 2026CVE-2026-52823
Kimai: Login CSRF in the Timesheet Stop and Restart API Endpoints Allows Unauthorized State Changes
medium5.3Jul 14, 2026CVE-2026-52824
Kimai: Default APP_SECRET in Docker Image Enables Cookie Forgery and Account Takeover
critical9.1Jul 14, 2026CVE-2026-52825
Kimai has Improper Authorization in Team Member and Team Activity Assignment APIs Which Allows Expansion of Team Scope Beyond Authorized Visibility
medium5.3Jul 14, 2026CVE-2026-52826
Kimai: Improper Authorization in Project, Customer, and Activity Rate Edit Endpoints Allows Cross-Scope Rate Manipulation
medium5.3Jul 14, 2026
