Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the CanUpdate check at pkg/models/project_permissions.go:139-148 only requires CanWrite on the new parent project when changing parent_project_id. However, Vikunja's permission model uses a recursive CTE that walks up the project hierarchy to compute permissions. Moving a project under a different parent changes the permission inheritance chain. When a user has inherited Write access (from a parent project share) and reparents the child project under their own project tree, the CTE resolves their ownership of the new parent as Admin (permission level 2) on the moved project. This vulnerability is fixed in 2.3.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LVikunja
APPVikunja< 2.3.0
Related vulnerabilities
Vikunja: wielokrotne użycie tokenu resetowania hasła — przejęcie konta
Vikunja: słabe hasła i brak unieważniania sesji po zmianie hasła
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the OIDC callback handler issu...
Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, a flaw in Vikunja’s pa...
Vikunja is an open-source self-hosted task management platform. Starting in version 0.18.0 and prior to versio...