Vikunja
Vikunja before 2.7.1 Auth Token Leak via API URL Change
Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend API URL. Because checkAndSetApiUrl leaves origin-independent localStorage tokens in place, the bearer token and desktop OAuth refresh token are sent to the attacker's server, enabling account takeover.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.6high · scored by CNA · CWE-201
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.