Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vikunja | Vikunja | < 2.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/go-vikunja/vikunja/commit/6a0f39b252a81fa4b19dc56dc889183acc9Patch
- https://github.com/go-vikunja/vikunja/pull/2584Issue Tracking
- https://github.com/go-vikunja/vikunja/releases/tag/v2.3.0Release Notes
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-v479-vf79-mg83ExploitVendor Advisory
FAQ
What is CVE-2026-40103?
CVE-2026-40103 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 projec...
How severe is CVE-2026-40103?
CVE-2026-40103 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-40103?
Check the references section above for vendor advisories and patch information. Affected products include: Vikunja Vikunja.