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.
The Grav Form plugin versions 1.1.0 up to but not including 9.1.40 contain a stored cross-site scripting (XSS) vulnerability in the Form::uploadFiles() function. This vulnerability arises because the plugin sanitizes SVG files only when the file's last extension is .svg, allowing files with additional extensions (e.g., drawing.svg.foo) to bypass sanitization. An anonymous attacker can exploit this by uploading malicious files through public upload forms, which execute scripts in an administrator's session when opened. This can lead to the creation of a super-admin account on Grav 2.x installations using Admin2.
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 unvalidated input to move files outside the intended directory, potentially writing files or creating directories in arbitrary writable locations, including the web root.
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 code via the STREET profile field. This injected script executes when role managers hover over the address icon in the members_assignment_data.php page, potentially compromising their session.
The 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 to a theme's Twig templates folder via the blueprint-upload endpoint. By including the uploaded file in sandboxed page Twig templates, an attacker can execute arbitrary commands with the privileges of the web-server user.
Admidio versions before 5.0.18 have a vulnerability in session expiration handling that allows attackers to maintain access to an account after a password reset. The flaw occurs because the password reset process deletes sessions based on the visitor ID rather than the user ID, enabling attackers with an existing session or remember-me cookie to continue authenticated access post-reset.
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. These scripts execute in the context of the Admidio origin when the SVG is served inline by the downloadFile() function without appropriate security headers like nosniff or Content Security Policy (CSP). This can affect all viewers of the SVG, including unauthenticated visitors.
SiYuan versions prior to 3.8.10 have an authentication bypass vulnerability. This flaw allows unauthenticated attackers to gain Administrator privileges by spoofing the X-Forwarded-For header through a trusted reverse proxy configured to trust loopback addresses. Exploitation requires sending requests with the Host header set to localhost and X-Forwarded-For set to 127.0.0.1. Attackers can then access private note history contents via the /history/*path route if no lock-screen password is set.
Admidio versions from 5.0.17 up to but not including 5.0.18 contain a missing authorization vulnerability. This flaw allows authenticated regular users to upload images into the announcements module by exploiting the CKEditor upload handler. Attackers can store images under adm_my_files/announcements/images and retrieve them via show_image.php, effectively abusing the application as an image host.
SiYuan versions from 3.6.0 up to but not including 3.8.10 contain an information disclosure vulnerability. Authenticated users with Reader privileges can exploit this flaw to access protected document contents by leveraging block-reference footnote resolution during Markdown export. This allows disclosure of body text from hidden, disabled, or password-protected documents without needing the publish password.
Parse Server versions before 8.6.122 and 9.0.0 before 9.11.1-alpha.2 allow modification of certain fields using dot notation keys, bypassing beforeSave trigger protections. This affects Object, Array, GeoPoint, Polygon, Bytes (on MongoDB), and ACL fields during create and update operations. An authorized client can exploit this to alter fields intended to remain constant, potentially bypassing Cloud Code authorization checks.