CVE-2026-134282
Summary
by MITRE • 11/21/2026
Vikunja from 0.14.0 before 2.8.0 contains a mass assignment vulnerability that allows authenticated users to set json-hidden fields by sending XML request bodies to the v1 API. Attackers can set BackgroundFileID on project creation to download any stored file via the background endpoint, or create bots with IsAdmin set to gain instance-admin access.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The identified vulnerability in Vikunja versions prior to 2.8.0 represents a critical mass assignment flaw within its REST API implementation, specifically affecting authenticated users who interact with the v1 API endpoints using XML request bodies. Mass assignment vulnerabilities occur when an application automatically binds incoming input parameters from HTTP requests directly to properties of server-side objects without sufficient validation or filtering. In this specific instance, the vulnerability stems from the backend framework's default behavior of mapping all provided JSON-like fields in the serialized payload to corresponding model attributes, regardless of whether those fields are intended for public modification or marked as hidden in standard API documentation. This architectural oversight allows an authenticated attacker to bypass intended access controls by injecting parameters that are typically restricted to administrative operations or internal system processes.
The technical mechanism exploits the lack of strict allow-listing for input fields during object instantiation and update operations. When a user sends an XML request body, the parser deserializes the data into a server-side object structure. Because the framework does not explicitly exclude certain sensitive properties from this binding process, attributes such as BackgroundFileID and IsAdmin become modifiable by any authenticated actor. This is particularly dangerous because it circumvents the application's logical security boundaries that are usually enforced through UI constraints or API route restrictions. The vulnerability effectively grants lower-privileged users the ability to manipulate internal state variables that should remain immutable except under strict administrative oversight, thereby breaking the principle of least privilege inherent in secure system design.
The operational impact of this flaw is severe and multifaceted, primarily manifesting as unauthorized data access and complete compromise of instance integrity. By manipulating the BackgroundFileID field during project creation or modification, an attacker can trigger background file processing routines that expose arbitrary files stored within the application's filesystem to external download endpoints. This leads to a direct confidentiality breach, allowing attackers to retrieve sensitive documents, configuration files, or user data that were not intended for public consumption. Furthermore, the ability to set the IsAdmin flag on new bot accounts enables privilege escalation attacks. An attacker can create a new account with elevated privileges equivalent to an instance administrator, granting them full control over the Vikunja installation. This includes the ability to manage users, modify global settings, and potentially execute further malicious actions depending on the underlying infrastructure's exposure.
From a classification perspective, this vulnerability aligns closely with CWE-915, which describes Improper Control of Dynamically-Managed Code Resources, specifically falling under the sub-category of mass assignment flaws where input from an upstream component is used to control internal system resources without proper validation. It also maps to MITRE ATT&CK technique T1078, Valid Accounts, as it relies on existing authentication credentials to perform unauthorized actions, and potentially T1098, Account Manipulation, due to the ability to create accounts with administrative privileges. The exploitation path demonstrates a failure in input validation logic where trusted sources are assumed safe without verifying that only expected fields are being processed by the backend object mapper.
Mitigation strategies must focus on immediate patching and architectural hardening of API endpoints. The primary remediation is upgrading Vikunja to version 2.8.0 or later, where this mass assignment vulnerability has been addressed through stricter input filtering mechanisms. In environments where immediate patching is not feasible, temporary mitigations should include implementing a reverse proxy rule that restricts the HTTP methods allowed on affected endpoints and validating Content-Type headers to ensure only expected formats are processed with rigorous schema validation. Additionally, developers should review all API controllers to enforce explicit allow-lists for input fields rather than relying on implicit binding behaviors. Implementing robust logging and monitoring for unusual patterns in XML payload sizes or frequent attempts to set administrative flags can also aid in early detection of exploitation attempts before significant damage occurs.