Vikunja before 2.7.1 Auth Token Leak via API URL Change
- Exploited
- No known exploitation
- Fix
- Fixed in 2.7.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Vikunja versions up to and including 2.7.0 (affected versions <= 2.7.0). The victim must be logged in and be led to switch the frontend API URL to an attacker's server.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Vikunja, the open-source task management software, before version 2.7.1 can leak users' stored login tokens to an attacker-controlled server if a user is tricked into switching the frontend API URL, which could allow account takeover. The attack can be launched remotely without logging in, but it requires the victim to take an action.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.6/10CVSS 7.6
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Vikunja versions up to and including 2.7.0 (affected versions <= 2.7.0). The victim must be logged in and be led to switch the frontend API URL to an attacker's server.Upgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
fixed in 2.7.1
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123513
Is CVE-2026-123513 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A logged-in Vikunja user who is tricked into switching the frontend's API URL to an attacker's server can have their bearer token sent to that server. On desktop, a refresh token can be sent as well, and the attacker can use it to act as the victim on the real instance.Source: github.com
Which versions are affected by CVE-2026-123513?
vikunja: before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions up to and including 2.7.0 are affected. To check, look at the Vikunja version you run; the advisory's affected range is 2.7.0 and older. The issue requires a user to be logged in and to change the frontend API URL to a different server.Source: github.com
How do I fix CVE-2026-123513?
Upgrade to Vikunja 2.7.1 or later, which contains the fix.Source: github.com