Unrated

CSRF in Kimai team creation and assignment endpoints

IdentifiersCVE-2026-49992CWE-352

CVE-2026-49992 is an authenticated cross-site request forgery vulnerability in Kimai affecting default team creation and related assignment endpoints. The issue allows state-changing actions to be triggered through vulnerable GET-based administrative routes, enabling unauthorized creation or reuse of teams, assignment of the victim user as teamlead, and rebinding of projects, customers, or activities to teams. Successful exploitation depends on inducing a logged-in user with sufficient permissions to load attacker-controlled content, after which Kimai processes the forged requests as if they were initiated intentionally by the authenticated victim. The flaw can alter authorization structure and team-based object relationships in a persistent manner.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to cause unauthorized persistent administrative changes within Kimai under the security context of the targeted authenticated user. This includes creating or reusing teams, assigning teamlead roles, and changing team associations for projects, customers, or activities. These changes can affect visibility controls, assignment boundaries, team-based access control, and reporting integrity, and may create conditions for subsequent privilege expansion or abuse of authorization logic.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, limit access to the affected administrative functionality, minimize exposure of privileged Kimai sessions, and ensure administrators avoid visiting untrusted or attacker-controlled web content while authenticated. Standard CSRF hardening practices for administrative workflows should also be enforced where possible until the fixed version is deployed.

Remediation

Patch, then assume compromise.

Upgrade Kimai to version 2.58.0 or later. The vendor fix replaces the vulnerable state-changing GET routes with API POST endpoints, reducing exposure to cross-site request forgery for these operations.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

KimaiKimaiapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity