CyberRota Analysis
AI-GeneratedThe vulnerability in Vikunja allows authenticated users to duplicate projects under arbitrary parent projects without proper permission checks, potentially enabling unauthorized content injection into other users' or teams' project hierarchies. This flaw affects versions 0.21.0 to 2.4.0 and poses a medium risk, particularly for organizations using Vikunja for task management. Users of affected versions should prioritize upgrading to version 2.4.0 to mitigate this security risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Vikunja is an open-source self-hosted task management platform. From 0.21.0 until 2.4.0, the project duplication operation in pkg/models/project_duplicate.go allows an authenticated user who can read a source project to place its duplicate beneath an arbitrary target parent project. ProjectDuplicate.CanCreate calls parent.CanCreate on an unhydrated Project containing only the body supplied parent_project_id instead of calling parent.CanWrite, so the target parent write-permission check is skipped. The ordinary project creation path enforces that permission, but PUT /api/v1/projects/{project}/duplicate does not, allowing attacker-owned content to be injected into another user or team project hierarchy. This issue is fixed in version 2.4.0.