CyberRota Analysis
AI-GeneratedVikunja versions 0.22.0 through 2.3.0 are vulnerable due to improper validation of principal types in API token management, allowing authenticated attackers to exploit numeric user IDs and link-share IDs. This vulnerability enables attackers to manipulate link-share JWTs to access, create, and delete a target user's API tokens, potentially compromising user accounts and permissions. Organizations using affected versions should prioritize upgrading to version 2.4.0 to mitigate this high-severity 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 versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.