CVE-2026-49992 Kimai: Login CSRF in Default Team Creation Endpoints Allows Unauthorized Team and Permission Structure Changes
Attackers can trick logged-in users into modifying team structures and permissions via CSRF in Kimai time tracking application.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-49992?
CVE-2026-49992 is a medium-severity vulnerability in kimai, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Kimai is an open-source time tracking application. Versions prior to 2.58.0 contain authenticated cross-site request forgery issues in their default team creation shortcuts for projects, customers, and activities. These endpoints are exposed through `GET` routes and directly create or reuse a `Team`, add the current user as teamlead, and bind the target object to that team. As a result, an attacker can trick a logged-in user with the required permissions into visiting a malicious page and cause unauthorized changes to team, teamlead, and object-binding relationships. This is a real authorization-structure modification issue rather than a harmless UI shortcut. Version 2.58.0 patches the issue.
Weakness: CWE-352
Which versions are affected by CVE-2026-49992?
2 open source packages ship an affected version, including kimai/kimai.
| Package | Affected | Fixed in |
|---|---|---|
kimai/kimai Packagist | All versions | 2.58.0 |
kimai/kimai Packagist | All versions | 2.58.0 |
How do I fix CVE-2026-49992?
Upgrade kimai/kimai to 2.58.0 or later.
Is CVE-2026-49992 being exploited?
There is no known exploitation of CVE-2026-49992 in the wild and no public exploit code.
Sources
Also known as GHSA-pgcc-vfmc-7cw5.