CVE-2026-134279 in Vikunja
Summary
by MITRE • 11/21/2026
Vikunja from 0.20.5 before 2.8.0 contains a login cross-site request forgery vulnerability in the OpenID Connect callback in OpenIdAuth.vue that accepts a valueless state parameter. Attackers can send a crafted callback link with an empty state and their own authorization code to silently log victims into the attacker's account and view the victims' entered data.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The identified vulnerability resides within the Vikunja application, specifically affecting versions ranging from 0.20.5 up to but not including version 2.8.0. This security flaw is classified as a Cross-Site Request Forgery attack targeting the OpenID Connect authentication callback mechanism implemented in the OpenIdAuth.vue component. The core technical deficiency lies in the improper validation of the state parameter during the OAuth2 authorization code flow. According to standard identity protocols, the state parameter serves as a critical CSRF token that must be generated by the client application and verified upon return from the identity provider to ensure that the authentication request originated from an authenticated user session rather than a malicious third-party site. In this instance, the implementation fails to enforce strict validation of the state value, allowing it to accept empty or missing values without triggering an error or rejecting the login attempt.
This technical flaw enables attackers to execute a sophisticated account takeover scenario by exploiting the trust relationship between the Vikunja application and its configured OpenID Connect identity provider. An attacker can craft a malicious URL that mimics a legitimate authentication callback but includes their own valid authorization code alongside an empty state parameter. When a victim, who is already authenticated with the identity provider or has active session cookies for it, clicks this link, the browser automatically sends the request along with any relevant credentials to the Vikunja backend. Because the application accepts the valueless state and validates only the presence of the authorization code, it successfully exchanges the attacker's code for a valid session token associated with the attacker's account rather than the victim's intended identity. Consequently, the victim is silently logged into the attacker's Vikunja instance without any further interaction or awareness.
The operational impact of this vulnerability is severe as it results in complete authentication bypass and unauthorized access to sensitive project data stored within the compromised account. Since Vikunja is a task management application often used for collaborative work containing proprietary information, personal schedules, and confidential documents, an attacker gaining control over a victim's session can exfiltrate this data or modify tasks maliciously. This attack vector does not require complex social engineering beyond luring a user to click a link, making it highly effective in phishing campaigns where the primary goal is account hijacking rather than immediate credential theft. The ability to silently log victims into an attacker-controlled environment undermines the fundamental integrity of the authentication process and compromises the confidentiality and availability of the application's data assets.
From a standards perspective, this vulnerability aligns with CWE-352, which describes Cross-Site Request Forgery, specifically highlighting the failure to verify anti-CSRF tokens in stateful HTTP requests. Furthermore, it relates closely to CWE-613, Insufficient Session Expiration, as the attack leverages existing valid sessions at the identity provider level. In terms of offensive security frameworks, this technique maps to MITRE ATT&CK Tactic TA0004 (Privilege Escalation) and specifically the sub-technique T1556.008, which covers Modifying Identity Provider Authentication Mechanisms. The exploitation relies on manipulating the authentication flow to assume a different identity, effectively bypassing access controls through protocol abuse rather than traditional injection or buffer overflow techniques.
To mitigate this vulnerability, immediate patching is required by upgrading Vikunja to version 2.8.0 or later where the state parameter validation has been corrected. For organizations unable to upgrade immediately due to compatibility constraints, implementing a Web Application Firewall rule that strictly validates the presence and format of the state parameter in OpenID Connect callback requests can provide temporary protection. Additionally, developers should ensure that all OAuth2 implementations rigorously validate the state parameter against previously generated values stored securely in the user's session before processing any authorization codes. Enforcing strict SameSite cookie attributes on application cookies further reduces the risk of such forgery attacks by preventing browsers from sending these credentials to third-party origins during cross-site requests. Regular security audits focusing on identity and access management flows are essential to detect similar misconfigurations in authentication logic across web applications.