Permission topology changes via state-changing GET routes
Published Sep 11, 2026 · Updated Sep 11, 2026
Cross-site request forgery in Kimai before 2.58.0 allows remote attackers to alter team permission relationships via a malicious page. The project, customer, and activity create_team GET routes create or reuse a Team, add the current user as teamlead, and bind the target object. Exploitation requires a logged-in user who can manage the targeted object's permissions and causes persistent authorization-structure changes without that user's intent.
Summary
What happened
Cross-site request forgery in Kimai before 2.58.0 allows remote attackers to alter team permission relationships via a malicious page. The project, customer, and activity create_team GET routes create or reuse a Team, add the current user as teamlead, and bind the target object. Exploitation requires a logged-in user who can manage the targeted object's permissions and causes persistent authorization-structure changes without that user's intent.
The record
- CVE
- CVE-2026-49992
- Published
- Sep 11, 2026
- Updated
- Sep 11, 2026
- Vendor
- Kimai
- Product
- Kimai
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2026CVE publishedPublication date reported by the CVE source.
- Sep 11, 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.58.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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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