Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-vikunja/vikunja/commit/6a0f39b252a81fa4b19dc56dc889183acc9225ae Patch
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf79-mg83 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.4 · vikunjaNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*
References 4
- https://github.com/go-vikunja/vikunja/commit/6a0f39b252a81fa4b19dc56dc889183acc9225ae Patch
- https://github.com/go-vikunja/vikunja/pull/2584 Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf79-mg83 Exploit, Vendor Advisory