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.
Affected products
vikunja: vikunja
References4
- github.com/go-vikunja/vikunja/security/advisories/GHSA-2vq4-854… ExploitVendor Advisory
- github.com/go-vikunja/vikunja/commit/c03d682f48aff890eeb3c8b41d… Patch
- github.com/go-vikunja/vikunja/pull/2583 Issue Tracking
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
Metrics
- CVSS 3.1
-
8.3
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L - EPSS — exploit probability
- 0% percentile: 22 · as of 12 November 2026
- CWE
- CWE-269
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.