Vikunja 0.18.0 before 2.7.1 Privilege Escalation via Account Deletion
- 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. Affected versions are vikunja 0.18.0 up to but not including 2.7.1 The attacker must run a team, and the project must be shared read-only with that team Bot deletion (the bots endpoint) is one trigger; the bug also occurs when a collaborator's account is deleted
- 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? →
- 15/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 from 0.18.0 before 2.7.1 contains a privilege escalation vulnerability that allows team owners to gain admin or ownership of read-only shared projects by deleting accounts. Attackers can create a bot, add it to their team, and delete it through the bots endpoint, triggering ensureProjectAdminUser to promote read-only shares and lock out the real owner.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are vikunja 0.18.0 up to but not including 2.7.1 The attacker must run a team, and the project must be shared read-only with that team Bot deletion (the bots endpoint) is one trigger; the bug also occurs when a collaborator's account is deletedUpgrade to a fixed version: 2.7.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- go-vikunja vikunja
From 0.18.0 · 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-123520
Is CVE-2026-123520 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?
When a user is deleted, Vikunja can wrongly leave that user's rights on shared projects in place, which lets a team owner gain admin rights on projects shared with that team, even read-only ones. The attacker can then edit or delete those projects, and with a direct read-only share can take ownership and lock out the real owner.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-123520?
vikunja: from 0.18.0 before 2.7.1.Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions from 0.18.0 up to but not including 2.7.1 are affected. The bug is triggered by deleting a bot account that was added to a team the attacker runs, and also happens by accident when a collaborator's account is deleted. To check your version, run the vikunja binary with its version flag or look at the version shown in the web interface.Source: vulncheck.com, github.com
How do I fix CVE-2026-123520?
Upgrade Vikunja to version 2.7.1 or later, which contains the fix.Source: vulncheck.com, github.com