CVE-2026-28685: Kimai: API invoice endpoint missing customer-level access control (IDOR)

Published Mar 4, 2026
·
Updated

Summary

GET /api/invoices/{id} only checks the role-based viewinvoice permission but does not verify the requesting user has access to the invoice's customer. Any user with ROLETEAMLEAD (which grants viewinvoice) can read all invoices in the system, including those belonging to customers assigned to other teams.

Affected Code

src/API/InvoiceController.php line 92-101:

php #[IsGranted('viewinvoice')] // Role check only, no customer access check #[Route(methods: ['GET'], path: '/{id}', name: 'getinvoice', requirements: ['id' => '\d+'])] public function getAction(Invoice $invoice): Response { $view = new View($invoice, 200); $view->getContext()->setGroups(self::GROUPSENTITY); return $this->viewHandler->handle($view); // Returns ANY invoice by ID }

The web controller (src/Controller/InvoiceController.php line 304-307) correctly checks customer access:

php #[IsGranted('viewinvoice')] #[IsGranted(new Expression("isgranted('access', subject.getCustomer())"), 'invoice')] public function downloadAction(Invoice $invoice, ...): Response { ... }

The access attribute in CustomerVoter (line 71-87) verifies team membership, but this check is entirely missing from the API endpoint.

PoC

Tested against Kimai v2.50.0 (Docker: kimai/kimai2:apache).

Setup: - TeamA with CustomerA ("SecretCorp"), TeamB with CustomerB ("BobCorp") - Bob is a teamlead in TeamB only - An invoice exists for SecretCorp (TeamA)

bash Bob (TeamB) reads SecretCorp (TeamA) invoice curl -H "Authorization: Bearer BOBTOKEN" http://localhost:8888/api/invoices/1

Response (200 OK): json { "invoiceNumber": "INV-2026-001", "total": 15000.0, "currency": "USD", "customer": {"name": "SecretCorp", ...} }

Bob can also enumerate all invoices via GET /api/invoices — the list endpoint uses setCurrentUser() in the query but the single-item endpoint bypasses this entirely via Symfony ParamConverter.

Impact

Any teamlead can read all invoices across the system regardless of team assignment. Invoice data typically contains sensitive financial information (amounts, customer details, payment terms). In multi-team deployments this breaks the intended data isolation between teams.

Suggested Fix

Add the customer access check to the API endpoint, matching the web controller:

diff #[IsGranted('viewinvoice')] +#[IsGranted(new Expression("isgranted('access', subject.getCustomer())"), 'invoice')] #[Route(methods: ['GET'], path: '/{id}', name: 'getinvoice')] public function getAction(Invoice $invoice): Response

Other sources

Kimai is a web-based multi-user time-tracking application. Prior to version 2.51.0, "GET /api/invoices/{id}" only checks the role-based viewinvoice permission but does not verify the requesting user has access to the invoice's customer. Any user with ROLETEAMLEAD (which grants viewinvoice) can read all invoices in the system, including those belonging to customers assigned to other teams. This issue has been patched in version 2.51.0.

MITRE

Affected Software

2 affected componentsFixes available
composer/kimai/kimai<=2.50.0
2.51.0
Kimai Kimai<2.51.0

Event History

Mar 4, 2026
Advisory Published
via GitHub·08:43 PM
Data Sourced
via GitHub·08:43 PM
DescriptionSeverityWeaknessAffected Software
Mar 6, 2026
CVE Published
via MITRE·04:49 AM
Data Sourced
via MITRE·04:49 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 AM
RemedyAffected Software
May 22, 58164
Event
via FIRST·07:07 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-28685?

CVE-2026-28685 is classified as a high-severity vulnerability due to improper access control that allows unauthorized access to sensitive invoice data.

2

How do I fix CVE-2026-28685?

To fix CVE-2026-28685, upgrade to remedy version 2.51.0 or later, which implements proper customer access checks.

3

What impact does CVE-2026-28685 have on affected systems?

CVE-2026-28685 allows users with 'ROLE_TEAMLEAD' to view all invoices, potentially exposing sensitive customer information.

4

Is CVE-2026-28685 present in earlier versions of the software?

Yes, CVE-2026-28685 affects all versions of kimai/kimai prior to 2.51.0.

5

Who is responsible for mitigating CVE-2026-28685?

It is the responsibility of system administrators and developers using kimai/kimai software to apply the necessary patches to mitigate CVE-2026-28685.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203