Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access

published 2026-10-09 30 d ago modified 2026-10-19 20 d ago also GHSA-r6w9-259g-gwrv , GO-2026-6748 , EUVD-2026-95994

cvss: 8.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits: 0; none known

Vikunja is an open-source self-hosted task management platform. Versions prior to 2.4.0 store password-reset, email-confirmation, and account-deletion tokens in the `user_tokens` table in plaintext. If an attacker gains read access to the database through a backup leak, misconfigured storage, or SQL-level exposure, they can immediately use pending tokens to take over user accounts without knowing passwords. Version 2.4.0 fixes the issue.

Patch / fix

fixed in 1 links 4

go code.vikunja.io/api 2.4.0

github.com/go-vikunja/vikunja@00fd2c6 commit
github.com/go-vikunja/vikunja@3a0ea15 commit
github.com/go-vikunja/vikunja@e31ea2d commit
github.com/go-vikunja/vikunja/releases/tag/v2.4.0 release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: total
Assessed: 26 d ago (2026-10-13)

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/go-vikunja/vikunja/security/advisories/GHSA-r6w9-259g-gwrv referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	8.1	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
go	code.vikunja.io/api	<2.4.0 all versions	2.4.0

Affected products

go-vikunja vikunja

Classification

Weakness

CWE-312 Cleartext Storage of Sensitive Information
CWE-916 Use of Password Hash With Insufficient Computational Effort

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary