Description
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.
Affected products
vikunja: vikunja
References4
- github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf7… ExploitVendor Advisory
- github.com/go-vikunja/vikunja/commit/6a0f39b252a81fa4b19dc56dc8… Patch
- github.com/go-vikunja/vikunja/pull/2584 Issue Tracking
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L - EPSS — exploit probability
- 0% percentile: 13 · as of 12 November 2026
- CWE
- CWE-836
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.