Skip to main content
VulnerabilityPublished

CVE-2026-52820: Kimai · Timesheet PATCH/POST allows assigning to project outside user's team via query_builder OR-bypass

Affects kimai/kimaiSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.57.0 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.57.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.57.0.

Affected software

ProductAffectedFixed in
Packagistkimai/kimaiAffected
  • <2.57.0
Fixed in
  • 2.57.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the Timesheet API endpoints to trusted users only and monitor for suspicious timesheet project reassignments. Avoid exposing detailed project/customer metadata in API responses to unauthorized users. Follow vendor updates for an official fix.

Description

Kimai versions prior to 2.57.0 have a vulnerability in the Timesheet API PATCH and POST endpoints that allows authenticated users to assign their timesheets to projects outside their authorized teams. This occurs because the project ID submitted by the user bypasses team membership checks due to an unconditional OR condition in the query builder. Consequently, users can access project and customer metadata that should be restricted by team access controls.

References

Community reviews

Loading reviews…