Vikunja
Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.6high · scored by CNA · CWE-613
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
go-vikunja vikunja
- < 2.7.1
Fixed in 2.7.1
Mitigation
Upgrade vikunja to 2.7.1 or later.
References
- Vendor advisory github.com/go-vikunja/vikunja/security/advisor…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.