Vikunja versions from 0.16.0 up to but not including 2.8.0 have an information disclosure vulnerability. This flaw causes users' Trello API tokens to be written verbatim to application logs and Sentry error telemetry when Trello migration fails due to transport errors. The token is embedded in the URL error, exposing reusable third-party credentials to anyone with access to logs or telemetry data.
OpenRemote 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. Exploiting this, attackers can deploy JSON asset-scoped rulesets with custom asset IDs to generate high severity alarms and trigger operator notifications for arbitrary assets within the realm.
Vikunja versions from 0.17.0 up to but not including 2.8.0 have a vulnerability where the task.deleted notification and webhook payload include related tasks with the deleting user's permissions. This payload is sent to all project subscribers without checking authorization per recipient, potentially exposing private task data to unauthorized users subscribed to the project or owning its webhook.
Vikunja versions from 1.0.0 up to but not including 2.8.0 contain an account takeover vulnerability related to SSO identity hijacking. This occurs when the email fallback feature is enabled, allowing attackers to register or modify local accounts with unverified victim emails. As a result, the victim's first OpenID Connect (OIDC) login links to the attacker-controlled account, exposing the victim's data.
Vikunja versions from 2.2.1 up to but not including 2.8.0 have a vulnerability in the TOTP validation process. The flaw allows attackers with valid credentials to bypass replay protection by padding previously used TOTP codes with whitespace and resubmitting them within the code's validity window to gain a session token.
Vikunja versions from 0.14.0 up to but not including 2.8.0 have a mass assignment vulnerability. Authenticated users can exploit this by sending XML request bodies to the v1 API to set fields that are normally hidden in JSON. This allows attackers to set the BackgroundFileID during project creation to download any stored file or create bots with administrative privileges by setting IsAdmin, potentially gaining instance-admin access.
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 crash due to out-of-memory conditions during image preview processing.
Vikunja versions from 0.9.0 up to but not including 2.8.0 have an information disclosure vulnerability that allows project administrators to view email addresses of share creators. This occurs via the project shares endpoint, where the shared_by email field is accessible. The vulnerability exposes email addresses of creators, including those of former project members, to attackers with admin permissions.
Admidio versions prior to 5.0.18 have an insecure direct object reference (IDOR) vulnerability in the mylist.php script. This flaw allows authenticated users with access to the Lists module to read certain list configuration details of other users if they know the list's UUID. The vulnerability arises because the application verifies only the organization ownership but not the list owner or its privacy settings when loading list configurations.
Admidio versions 5.0.0 up to but not including 5.0.18 contain a path traversal vulnerability in the Documents & Files renameFile() function. 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 an uploaded SVG file containing malicious script to the web root, enabling stored cross-site scripting (XSS) attacks against administrators, potentially leading to account takeover.
Vikunja versions from 0.18.0 up to but not including 2.8.0 have a resource amplification vulnerability in the export functionality. Authenticated users can cause the server to exhaust memory by exporting tasks that are heavily related to a single task with a large description. This can lead to an out-of-memory crash affecting all users.
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 excessively large business-day operands in date math filters, causing a CPU exhaustion condition. This occurs due to a per-day loop in the go-datemath library that pins CPU cores and exhausts server resources.
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, which triggers quadratic string concatenation during CalDAV alarm parsing. This causes excessive memory and CPU consumption, potentially allocating gigabytes of memory during CalDAV reads, including automatic syncs by other users.
Admidio versions 5.0.0 through 5.0.17 contain a stored cross-site scripting (XSS) vulnerability that allows role administrators to inject malicious JavaScript code via specially crafted role names. This injected script executes when a full administrator views the affected profile page, enabling theft of the CSRF token and unauthorized assignment of the Administrator role.
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. Project readers or CalDAV clients can trigger this expansion, causing very large responses from small descriptions.
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 containing a very large number of parameters in a single line. This causes excessive CPU usage due to superlinear parsing before permission checks are performed, potentially exhausting server resources.
Vikunja versions from 0.21.0 up to but not including 2.8.0 contain a resource exhaustion vulnerability. Authenticated users can exploit this by setting a project position below 0.1, causing repeated instance-wide database writes. This triggers recalculation of project positions for all users' root projects, holding SQLite's write lock and degrading service availability.
Admidio versions from 5.0.2 up to but not including 5.0.17 contain an arbitrary file read vulnerability. This flaw allows any logged-in user to read sensitive server files by embedding local file paths in the img src attribute of eCard messages. Exploitation can disclose critical information such as database credentials and system files like /etc/passwd.
Admidio versions 5.0.0 up to but not including 5.0.18 have an improper authorization vulnerability in the modules/profile/profile_new.php component. This flaw allows authenticated Group Leaders to bypass field-level profile restrictions, enabling them to read and modify restricted member profile fields via specific request modes.
The Grav API plugin versions from 1.0.16 up to but not including 1.1.11 contain an authorization bypass vulnerability. This flaw allows holders of scoped API keys to override page permission rules because the system checks the owning account's authority rather than the API key's specific scopes. Consequently, attackers with keys minted on super-admin accounts can perform unauthorized edits, deletions, or reads on pages that normally deny such actions. Similarly, media-scoped keys can be used to modify media on pages that are intended to be read-only.