Vikunja
Vikunja 0.18.0 before 2.7.1 Privilege Escalation via Account Deletion
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CNA · CWE-269
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
go-vikunja vikunja
- >= 0.18.0, < 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.