https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-29T17:15:33.259543+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-52821 fkie_cve-2026-52821 2026-09-29T17:15:33.261375+00:00

Kimai is an open-source time tracking application. Prior to 2.57.0, GET or POST requests to /en/admin/activity/create/{project} and /en/admin/project/create/{customer} require only the generic create_activity or create_project capability and do not verify edit access to the supplied Project or Customer object. A user who knows a valid project.id or customer identifier can use the preset-parent creation logic in src/Controller/ActivityController.php or src/Controller/ProjectController.php to persist a new child business object under an unauthorized parent, polluting project or customer configuration and influencing later time-entry, rate, reporting, and billing behavior. This issue is fixed in version 2.57.0.

 https://vulnerability.circl.lu/vuln/ghsa-3q6q-26vg-v97x GHSA-3q6q-26vg-v97x — Kimai: Improper Authorization Through Activity Creation with Preset Project Allows Creation Under Unauthorized Projects 2026-09-29T17:15:33.261455+00:00

Affected: Packagist: kimai/kimai

### Summary

Kimai 2.56.0 contains an authenticated improper authorization vulnerability in the preset-project activity creation flow. A user with the generic `create_activity` permission, but without access to a target project, can still create a new `Activity` under that unauthorized project by visiting the preset project creation route directly.

This is a persistent cross-project business-object creation issue. The attacker does not need permission to view or edit the target project and only needs to know a valid `project.id`.

### Details

The issue affects the activity creation entry point that accepts a preset project identifier:

- `GET/POST /en/admin/activity/create/{project}` - `GET/POST /en/admin/project/create/{customer}`

In `src/Controller/ActivityController.php`, the controller checks only the global capability to create activities and does not verify whether the current user is allowed to create an activity under the supplied `Project` object.

The form and repository path also preserve the preset project instead of rejecting it when the user lacks access. Because the preset project is merged into the candidate set, the final save operation can persist a new `Activity` under a project that is outside the attacker's authorized project scope.

The same logic applies to the `src/Controller/ProjectController.php`.

*A PoC was provided, but removed for security reasons.*

### Impact

This vulnerability allows an authenticated user to inject new child business obj…