Grav API plugin versions from 1.0.0 up to but not including 1.1.4 contain a remote code execution vulnerability. This flaw allows users with media and page write permissions to upload files into a theme's Twig templates folder via the blueprint-upload endpoint. These uploaded files can then be included and executed within sandboxed page Twig templates, resulting in command execution as the web-server user. The vulnerability is fixed in version 1.1.4.
Admidio versions from 5.0.0 up to but not including 5.0.18 contain a path traversal vulnerability in the DocumentsService::renameFile() function. Authenticated users with folder upload permission can exploit this flaw by supplying crafted adm_new_name values containing '../' sequences, allowing them to move files outside the intended adm_my_files directory. This enables writing files and creating directories in arbitrary writable locations, including the web root. The vulnerability is rated high severity with a CVSS 4.0 score of 7.1. A fix is available in version 5.0.18.
Admidio versions from 5.0.17 up to but not including 5.0.18 contain a stored cross-site scripting (XSS) vulnerability. Authenticated users can inject malicious JavaScript into the STREET profile field, which is not properly neutralized during web page generation. This injected script executes when role managers hover over the address icon, exploiting an unencoded title attribute in members_assignment_data.php. The vulnerability is fixed in version 5.0.18.
Admidio versions from 5.0.17 up to but not including 5.0.18 have a missing authorization vulnerability in the announcements module. Authenticated regular users can exploit the CKEditor upload handler to upload images without proper authorization. This allows attackers to store images under adm_my_files/announcements/images and retrieve them via show_image.php, effectively abusing the application as an image hosting service.
Admidio versions prior to 5.0.18 have a session management vulnerability where sessions are not properly invalidated after a password reset. This allows attackers who already possess a victim's session or remember-me cookie to maintain access to the account even after the victim changes their password.
Admidio versions 5.0.0 up to but not including 5.0.18 contain a path traversal vulnerability in the Documents & Files renameFile() action. Authenticated users with folder upload rights can exploit this flaw by using ../ sequences in the adm_new_name parameter to move files outside the intended directory. This allows attackers to relocate malicious SVG files containing scripts to the web root, enabling stored cross-site scripting attacks against administrators that can lead to account takeover.
Admidio versions from 5.0.16 up to but not including 5.0.18 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows users with folder upload permissions to upload SVG files containing malicious JavaScript. The vulnerable function serves these SVG files inline without appropriate security headers such as nosniff or Content Security Policy (CSP), enabling script execution in the context of the Admidio origin for all viewers, including unauthenticated visitors. The issue is fixed in version 5.0.18.
Admidio versions 5.0.0 through 5.0.17 contain an improper authorization vulnerability in the profile management module. Authenticated Group Leaders can bypass field-level profile restrictions to read and modify restricted profile fields by exploiting specific request modes. This issue is fixed in version 5.0.18.
Admidio versions 5.0.17 up to but not including 5.0.18 contain an authorization bypass vulnerability in the Lists module. Authenticated users with access to the Lists module can use a list UUID to access list configurations belonging to other users within the same organization. This allows reading of list names, selected profile fields, sort orders, and filter conditions without proper ownership or privacy checks.
Admidio versions 5.0.0 through 5.0.17 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows role administrators to inject malicious JavaScript code into role names, which are rendered without proper encoding in a profile page attribute. When a full administrator views the affected profile page, the injected script can execute, enabling theft of the CSRF token and unauthorized assignment of the Administrator role. The vulnerability is fixed in version 5.0.18.
Admidio versions from 5.0.2 up to but not including 5.0.17 contain a path traversal vulnerability that allows any logged-in user to read arbitrary server files. This is achieved by embedding local file paths in the img src attributes of eCard messages, which are processed and embedded by the sendEcard() function. Exploitation can lead to disclosure of sensitive files such as configuration files containing database credentials and system files like /etc/passwd. The vulnerability is fixed in version 5.0.17.
Vikunja versions from 2.4.0 up to but not including 2.8.0 contain a denial of service vulnerability in the richtext converter. Authenticated project writers can exploit this by storing tables with unbounded rowspan and colspan values, which can exhaust server memory and CPU resources. Project readers or CalDAV clients can trigger this resource exhaustion by reading markdown tasks, performing CalDAV GET requests, or using the frontend editor, resulting in very large responses disproportionate to the original content size.
Vikunja versions from 0.19.0 up to but not including 2.8.0 contain a denial of service vulnerability. Authenticated users can exploit this by supplying unbounded business-day operands in datemath filters, causing a CPU exhaustion via a loop in the go-datemath library. The issue is fixed in version 2.8.0.
Vikunja versions from 0.21.0 up to but not including 2.8.0 contain a denial of service vulnerability. Authenticated users can exploit this by creating tasks with many reminders and long titles, triggering quadratic string concatenation in the ParseAlarms function. This leads to excessive memory and CPU consumption during CalDAV reads, affecting all users syncing with the server. The issue is fixed in version 2.8.0.
Vikunja versions from 0.21.0 up to but not including 2.8.0 have a resource exhaustion vulnerability. Authenticated users can exploit this by setting a project position below 0.1, causing repeated database writes that hold SQLite's write lock and degrade service availability. This vulnerability is fixed in version 2.8.0.
Vikunja versions from 0.18.0 up to but not including 2.8.0 contain a resource amplification vulnerability that allows authenticated users to exhaust server memory by exporting tasks with many related tasks having large descriptions. This can cause an out-of-memory crash affecting all users. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 0.19.0 up to but not including 2.8.0 have a denial of service vulnerability. Authenticated CalDAV users can exploit this by uploading VTODO properties with an excessive number of parameters, causing excessive CPU consumption due to superlinear parsing before permission checks.
Vikunja versions from 1.0.0 up to but not including 2.8.0 have a memory exhaustion vulnerability. Authenticated users can exploit this by uploading extremely wide images as task attachments, causing the server to allocate excessive memory during image preview generation and crash repeatedly. This issue is fixed in version 2.8.0.
Vikunja versions from 0.9.0 up to but not including 2.8.0 have an information disclosure vulnerability. Project administrators with admin permissions can access the project shares endpoint and view the email addresses of share creators, including those of former project members. This exposure occurs via the shared_by email field in the link share list endpoint. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 2.6.0 up to but not including 2.8.0 have a resource exhaustion vulnerability in the Planka migration converter. This flaw allows an attacker controlling a Planka server to cause Vikunja to allocate excessive memory by returning boards with duplicate list IDs and many cards, potentially leading to an out-of-memory (OOM) kill of the Vikunja process. The issue is fixed in version 2.8.0.