Vikunja persistent access via revoked tokens in OAuth and API token creation
go-vikunja vikunja
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go-vikunja vikunja |
|
|
Original description
Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access tokens to keep authenticating because SetupTokenMiddleware skips session and account-status checks. Attackers with a stolen token can, after logout, password reset, or account disabling, mint OAuth sessions via /oauth/authorize or tk_ API tokens for persistent access.
From the CVE record · VulnCheck