Description
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.
Problem types
CWE-269: Improper Privilege Management
Product status
References
github.com/...ikunja/security/advisories/GHSA-2vq4-854f-5c72
github.com/go-vikunja/vikunja/pull/2583
github.com/...ommit/c03d682f48aff890eeb3c8b41d38226069722827
github.com/go-vikunja/vikunja/releases/tag/v2.3.0