CVE-2026-33316 | go-vikunja up to 2.1.x Password Reset token ResetPassword access control

VDB-352793 · CVE-2026-33316 · GCVE-0-2026-33316 GO-VIKUNJA UP TO 2.1.X PASSWORD RESET TOKEN RESETPASSWORD ACCESS CONTROL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.0 $0-$5k 2.14+ Summaryinfo A vulnerability was found in go-vikunja vikunja up to 2.1.x. It has been rated as critical. Affected by this issue is the function ResetPassword of the file /api/v1/user/password/token of the component Password Reset Handler. The manipulation leads to access control. This vulnerability is listed as CVE-2026-33316. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised. Detailsinfo A vulnerability, which was classified as critical, has been found in go-vikunja vikunja up to 2.1.x. This issue affects the function ResetPassword of the file /api/v1/user/password/token of the component Password Reset Handler. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is: Vikunja is an open-source self-hosted task management platform. Prior to version 2.2.0, a flaw in Vikunja’s password reset logic allows disabled users to regain access to their accounts. The `ResetPassword()` function sets the user’s status to `StatusActive` after a successful password reset without verifying whether the account was previously disabled. By requesting a reset token through `/api/v1/user/password/token` and completing the reset via `/api/v1/user/password/reset`, a disabled user can reactivate their account and bypass administrator-imposed account disablement. Version 2.2.0 patches the issue. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-33316 since 03/18/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue. Upgrading to version 2.2.0 eliminates this vulnerability. Productinfo Vendor go-vikunja Name vikunja Version 2.0 2.1 Website Product: https://github.com/go-vikunja/vikunja/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 7.2 VulDB Meta Temp Score: 7.0 VulDB Base Score: 6.3 VulDB Temp Score: 6.0 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.1 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Access control CWE: CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: vikunja 2.2.0 Timelineinfo 03/18/2026 CVE reserved 03/24/2026 +6 days Advisory disclosed 03/24/2026 +0 days VulDB entry created 03/24/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33316 (🔒) GCVE (CVE): GCVE-0-2026-33316 GCVE (VulDB): GCVE-100-352793 Entryinfo Created: 03/24/2026 16:11 Changes: 03/24/2026 16:11 (66) Complete: 🔍 Cache ID: 99:9DA:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸