CVE-2026-62376

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

Published Oct 9, 2026 CVSS 3.1 · 8.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Vikunja versions before 2.4.0 store sensitive password‑reset, email‑confirmation, and account‑deletion tokens in the user_tokens table as plaintext, creating a direct path for attackers to assume user accounts. If an adversary can read the database—through a backup leak, misconfigured storage, or a SQL‑level exposure—they can immediately use the exposed tokens to reset passwords or confirm email addresses without any password knowledge. This flaw falls under CWE‑312 (Plaintext Storage of Sensitive Data) and CWE‑916 (Information Exposure to Untrusted Entities). The potential impact is full account takeover, exposing all data and allowing further lateral movement within the environment.

Affected Systems

The affected product is go‑vikunja Vikunja. All releases prior to v2.4.0 are vulnerable; the issue is fixed in v2.4.0 and later versions.

Risk and Exploitability

The vulnerability carries a CVSS score of 8.1, indicating high severity, and is not listed in CISA’s KEV catalog. The EPSS score is not available, but the required condition is only read access to the database. Once read access is achieved—via leaked backups, insecure configuration, or an SQL injection that grants data retrieval—the attacker can directly perform account takeover, making this flaw likely to be exploited in scenarios where database protection is weak. Prevention hinges on securing database access rather than preventing the database from being readable by attackers.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Vikunja version 2.4.0 or later.
  • Revoke all existing password‑reset, email‑confirmation, and account‑deletion tokens by purging the user_tokens table or respecting any implemented expiration. Instruct users to reset passwords or re‑confirm emails if necessary.
  • Restrict database read permissions to trusted processes and users to prevent accidental exposure through backups or misconfiguration.

Generated by OpenCVE AI on October 9, 2026 at 22:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-r6w9-259g-gwrv Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Go-vikunja
Go-vikunja vikunja
Vendors & Products Go-vikunja
Go-vikunja vikunja
Type Values Removed Values Added
Description 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.
Title Vikunja: Plaintext storage of password-reset/email-confirm tokens in database enables account takeover on DB read access
Weaknesses CWE-312
CWE-916
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-312

    Cleartext Storage of Sensitive Information

  • CWE-916

    Use of Password Hash With Insufficient Computational Effort

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 13, 2026, 6:31 PM
Reserved
Jul 13, 2026, 10:04 PM
Status
Deferred
Published
Oct 9, 2026, 9:17 PM
Modified
Oct 16, 2026, 8:04 PM