Cross-team invoice disclosure via missing customer check
Published Mar 6, 2026 · Updated Mar 6, 2026
Improper authorization in Kimai before 2.51.0 allows remote authenticated users with ROLE_TEAMLEAD to read invoices across teams. The GET /api/invoices/{id} action in src/API/InvoiceController.php checks view_invoice but returns the selected invoice without invoking the customer's access voter. A team lead can supply another team's invoice identifier and receive financial and customer details, but cannot modify records through this read-only request.
Summary
What happened
Improper authorization in Kimai before 2.51.0 allows remote authenticated users with ROLE_TEAMLEAD to read invoices across teams. The GET /api/invoices/{id} action in src/API/InvoiceController.php checks view_invoice but returns the selected invoice without invoking the customer's access voter. A team lead can supply another team's invoice identifier and receive financial and customer details, but cannot modify records through this read-only request.
The record
- CVE
- CVE-2026-28685
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- Kimai
- Product
- Kimai
- Classifications
- CWE-285, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.51.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- GitHub advisory cross-team invoice proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo