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.
Vikunja versions from 0.8.0 up to but not including 2.8.0 contain a denial of service vulnerability. Authenticated project readers can exploit this by sending CalDAV PROPFIND requests with repeated calendar-data properties, causing excessive resource consumption. This can exhaust server memory, CPU, and bandwidth, leading to service disruption. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 2.2.1 up to but not including 2.8.0 contain a vulnerability in the TOTP validation process that allows attackers to bypass replay protection by padding consumed one-time passcodes with whitespace. An attacker with valid credentials who observes a used TOTP code can reuse it with added whitespace within the validity window to gain a session token.
Vikunja versions from 0.16.0 up to but not including 2.8.0 contain a vulnerability where users' Trello API tokens are written to application logs and Sentry. This occurs because provider errors are formatted verbatim in listeners.go, exposing tokens embedded in URL error messages during Trello migration failures. The vulnerability allows anyone with access to logs or telemetry data to obtain these reusable third-party credentials. The issue is fixed in version 2.8.0.
Vikunja versions 2.3.0 through 2.7.x contain a vulnerability in the CSV migration module where memory allocation is uncontrolled due to lack of de-duplication of label column mappings and no cap on labels per row. Authenticated users can exploit this by sending a specially crafted request to the migration endpoint, causing the server to exhaust memory and potentially crash.
Vikunja versions from 0.20.5 up to but not including 2.8.0 have a login cross-site request forgery (CSRF) vulnerability in the OpenID Connect callback component. This flaw allows attackers to craft a callback link with an empty state parameter and their own authorization code, which can silently log victims into the attacker's account and expose victim-entered data. The vulnerability is fixed in version 2.8.0. The CVSS 4.0 score is low (2.3), reflecting limited impact and attack complexity.
Vikunja versions from 0.17.0 up to but not including 2.8.0 have an incorrect authorization vulnerability. When a task is deleted, the notification and webhook payload include related tasks with the deleting user's permissions but are sent to all project subscribers without checking each recipient's authorization. This allows subscribers or webhook owners to receive full data of related tasks in private projects they normally cannot access.
Vikunja versions from 2.2.0 up to but not including 2.8.0 have an information disclosure vulnerability. Authenticated users can exploit the tasks.overdue webhook to access private project details of other users, including project titles, descriptions, and owner IDs. This occurs by registering a personal tasks.overdue webhook with a subscribed overdue task, which then leaks sensitive information to external URLs. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 0.14.0 up to but not including 2.8.0 have a mass assignment vulnerability allowing authenticated users to modify JSON-hidden fields via XML request bodies to the v1 API. This flaw permits attackers to set sensitive attributes such as BackgroundFileID to download stored files or IsAdmin to create bots with administrative privileges. The vulnerability is fixed in version 2.8.0.
Vikunja versions from 1.0.0 up to but not including 2.8.0 have an account takeover vulnerability related to improper authentication. Attackers can hijack Single Sign-On (SSO) identities by creating local accounts with unverified victim emails when the email fallback feature is enabled. This causes the victim's first OpenID Connect (OIDC) login to link to the attacker-controlled account, exposing the victim's data. The issue is fixed in version 2.8.0.
OpenRemote core versions from 1.2.0 up to but not including 1.34.0 have an authorization bypass vulnerability in the AlarmFacade component. This flaw allows users with write:rules permission to create alarms for assets outside their authorized ruleset subtree. Exploitation involves deploying a JSON asset-scoped ruleset with crafted asset IDs to generate high severity alarms and trigger operator notifications for arbitrary assets within the realm. The vulnerability has a medium severity score of 5.3 and was fixed in version 1.34.0.