Description
Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, the TOTP failed-attempt lockout mechanism is non-functional due to a database transaction handling bug. When a TOTP validation fails, the login handler in pkg/routes/api/v1/login.go calls HandleFailedTOTPAuth and then unconditionally rolls back. HandleFailedTOTPAuth in pkg/user/totp.go uses an in-memory counter (key-value store) to track failed attempts. When the counter reaches 10, it calls user.SetStatus(s, StatusAccountLocked) on the same database session s. Because the login handler always rolls back after a TOTP failure, the StatusAccountLocked write is undone. The in-memory counter correctly increments past 10, so the lockout code executes on every subsequent attempt, but the database write is rolled back every time. This allows unlimited brute-force attempts against TOTP codes. This vulnerability is fixed in 2.3.0.
Affected products
vikunja: vikunja
References5
- github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv9… ExploitVendor Advisory
- github.com/go-vikunja/vikunja/security/advisories/GHSA-fgfv-pv9… ExploitVendor Advisory
- github.com/go-vikunja/vikunja/commit/6ca0151d02fa0e8c7e2181ab91… Patch
- github.com/go-vikunja/vikunja/pull/2576 Issue Tracking
- github.com/go-vikunja/vikunja/releases/tag/v2.3.0 Release Notes
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 24 · as of 12 November 2026
- CWE
- CWE-307
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.