<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T14:18:52.539489+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-52819</id>
    <title>fkie_cve-2026-52819</title>
    <updated>2026-09-29T14:18:52.631323+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kimai is an open-source time tracking application. Prior to 2.57.0, the GET /api/timesheets list endpoint accepts user and users[] target identifiers from a caller with view_other_timesheet but does not apply access_user or verify that a ROLE_TEAMLEAD requester leads a team containing each target user. TimesheetController::cgetAction() adds the resolved users directly to the query while project and customer filtering still permits records on unscoped projects or projects sharing ordinary team membership, allowing a teamlead to retrieve another user's descriptions, timing data, tags, rate, and internalRate even though GET /api/timesheets/{id} would deny access through TimesheetVoter. This issue is fixed in version 2.57.0.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-52819"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-4m8q-55qv-9pwp</id>
    <title>GHSA-4m8q-55qv-9pwp — Kimai: Teamlead authorization bypass in GET /api/timesheets allows reading other users' timesheet records without being…</title>
    <updated>2026-09-29T14:18:52.631446+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: kimai/kimai</p>
<p>## Summary</p>
<p>`GET /api/timesheets?user=&lt;id&gt;` (and `users[]=&lt;id&gt;`) returns the targeted user's timesheet records to any caller that has the `view_other_timesheet` permission, without verifying that the caller is teamlead of any team containing the target user. The per-record endpoint `GET /api/timesheets/{id}` correctly enforces this check via `TimesheetVoter`/`RolePermissionManager::checkTeamAccessTimesheet` → `checkTeamLeadAccess`, but the list endpoint only filters projects/customers by team membership and never validates `t.user`. A `ROLE_TEAMLEAD` user can therefore enumerate any user's records — including the `rate` field — as long as those records are on a project with no team scoping (Kimai's default) or on any project that shares any team (membership, not lead) with the requester.</p>
<p>## Details</p>
<p>**Root cause:** authorization mismatch between the per-record voter and the list endpoint.</p>
<p>### Per-record path (correct)</p>
<p>`src/Voter/TimesheetVoter.php:138`:
```php
if (!$this-&gt;permissionManager-&gt;checkTeamAccessTimesheet($subject, $user)) {
    return false;
}
return $this-&gt;permissionManager-&gt;hasRolePermission($user, $permission . '_other_timesheet');
```</p>
<p>`checkTeamLeadAccess` (RolePermissionManager.php:143-160) requires `isTeamleadOf` (not just member) one of the **target user's** teams. The unit test `testTeamleadDeniedWhenOnlyPlainMemberOfOwnerTeam` (tests/Voter/TimesheetVoterTest.php:253-269) codifies this:</p>
<p>&gt; *"a TEAMLEAD role with `view_other_timesheet` must not access a…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-4m8q-55qv-9pwp"/>
  </entry>
</feed>
