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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sun, 08 Nov 2026 01:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Vikunja before 2.7.1 Auth Token Leak via API URL Change | |
| First Time appeared |
Vikunja
Vikunja vikunja |
|
| Weaknesses | CWE-201 | |
| CPEs | cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Vikunja
Vikunja vikunja |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-08T01:37:25.882Z
Reserved: 2026-11-06T00:46:28.480Z
Link: CVE-2026-123513
No data.
Status : Deferred
Published: 2026-11-08T02:16:40.013
Modified: 2026-11-08T02:16:40.140
Link: CVE-2026-123513
No data.
OpenCVE Enrichment
Updated: 2026-11-08T02:45:17Z
Weaknesses