SiYuan versions before 3.8.10 have an incomplete deny-list in the IsSensitivePath function that fails to block certain shell initialization files like .zshenv and .bash_profile, as well as the ~/.local directory. Authenticated administrators can exploit this by using the /api/file/copyFile endpoint to write files outside the workspace, which then execute with user privileges upon the next shell or login.
SiYuan versions from 3.3.0 up to but not including 3.8.10 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. When a crafted .sy.zip document is shared and rendered in the Electron desktop client with nodeIntegration enabled, it can execute arbitrary Node.js and host operating system commands. The vulnerability has a critical CVSS score of 9.6, indicating high impact on confidentiality, integrity, and availability.
SiYuan versions prior to 3.8.10 contain a stored cross-site scripting (XSS) vulnerability due to improper escaping of an Attribute View name in the database row attribute panel header. This vulnerability is an incomplete fix of CVE-2026-44670. An attacker able to persist the Attribute View name via the setAttrViewName action can inject an onerror handler that executes OS commands through Node.js when a desktop user opens the affected panel.
SiYuan versions prior to 3.8.10 have a stored cross-site scripting (XSS) vulnerability. This flaw allows attackers to inject malicious scripts via Attribute View column names that are rendered without proper escaping. The injection vectors include addAttributeViewKey, .sy.zip import, or synchronization features. When a victim adds or duplicates the affected column, the injected script executes with Node.js privileges, enabling desktop code execution.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated attackers to download data exports by reconstructing predictable file paths. Attackers can derive these paths using table id, base, table and view titles, and export time, enabling access to full exports including fields hidden from public shared views.
NocoDB versions prior to 2026.10.0 contain an SQL injection vulnerability that allows authenticated users with the Creator role to inject SQL during table creation. This is achieved by supplying a crafted formula parsed_tree, enabling attackers to execute malicious binary-expression operators interpolated into knex.raw fragments. Exploitation can lead to unauthorized reading of user and token tables and escalation to super administrator privileges on SQLite installations.
NocoDB versions from 0.253.0 up to but not including 2026.09.1 contain an authorization vulnerability in the baseUserDelete function. This flaw allows users with the Creator role to remove Owners, who have higher privileges, due to incorrect role power comparison logic. The vulnerability arises because the function getProjectRolePower returns -1 for the target Owner, which does not block the deletion request as intended. The issue has a low CVSS score of 2.7 and does not impact confidentiality or availability but can cause integrity loss by unauthorized user removal.
vLLM versions from 0.28.0 up to but not including 0.33.0 have an improper input validation vulnerability. This flaw allows unauthenticated attackers to crash the shared EngineCore by submitting out-of-range prompt token IDs when the service is run with the --skip-tokenizer-init option. By sending a large positive token ID to endpoints such as /v1/completions, /v1/embeddings, or /pooling, attackers can bypass the tokenizer's vocabulary check and trigger a fatal embedding index error, resulting in denial of service for all tenants.
vLLM versions prior to 0.33.0 have a path traversal vulnerability that allows malicious model publishers to redirect the served model and tokenizer by manipulating the verifier.name_or_path field in config.json. This can enable attackers to access local checkpoint directories, leak tokenizer vocabularies via unauthenticated /detokenize requests, and gain query access to private models.
NocoDB versions prior to 2026.10.1 contain a stored HTML injection vulnerability that permits authenticated users with record edit rights to inject malicious HTML content into rich text cells. The vulnerability arises because the sanitization relies solely on DOMPurify's default policy, which can be bypassed to insert forms, images, and styled overlays. Exploitation can lead to attackers embedding spoofed sign-in forms or remote images that harvest passwords and disclose viewer IP addresses in various views such as expanded records, gallery, kanban cards, and shared views.
NocoDB versions prior to 2026.10.1 have a template injection vulnerability that allows authenticated users with Creator role to execute arbitrary server-side JavaScript. This is achieved by supplying array-form property paths to Handlebars helpers in webhook templates, bypassing prototype guards and enabling execution of operating system commands or exfiltration of internal process data.
NocoDB versions prior to 2026.10.1 have a stored CSS injection vulnerability that allows authenticated users with Commenter or Editor roles to inject inline CSS styles. This is achieved by placing single quotes in mention text, which breaks out of the single-quoted data-id attribute in comments or rich text cells. The injected CSS can manipulate the interface layout or overlay elements for other users viewing the content.
NocoDB versions before 2026.10.1 have an authorization vulnerability that allows organization Creators to access routes meant for other roles. This flaw arises because the aclFn middleware does not enforce allowedRoles properly. Exploitation can lead to attackers generating super admin password reset links via org-users endpoints, enabling full instance takeover and unauthorized reading or modification of SSO client secrets.
Parse Server versions before 8.6.119 and 9.x before 9.10.8-alpha.3 have a missing authorization vulnerability. This flaw allows LiveQuery clients without the master key to subscribe to installation and internal classes. Exploiting this, attackers can obtain installation IDs and device tokens of other devices and modify those installations to redirect push notifications.
Craft CMS versions from 5.0.0 up to but not including 5.11.5 have a missing authorization vulnerability in the ChartsController::actionGetNewUsersData() method. This flaw allows authenticated control panel users to bypass the intended viewUsers permission check and retrieve aggregate user registration data for the site or any user group via a POST request.
A null pointer dereference vulnerability exists in ImageMagick versions before 7.1.2-35. This flaw can be triggered by using the -subimage option on a single-image list, causing the process to crash and resulting in a denial of service condition.
Craft CMS versions from 5.0.0 up to but not including 5.11.5 contain an SQL injection vulnerability. This flaw allows authenticated users with low privileges to inject raw SQL via nested array parameters in Element::findOne() criteria. Exploitation can occur through endpoints such as users/delete-address and users/save-address, enabling blind boolean or time-based SQL injection attacks to read database contents.
Craft CMS versions from 5.0.0 up to but not including 5.11.4 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows low-privilege control panel users to inject malicious JavaScript by manipulating cached license data. The vulnerability arises because the app/process-api-response-headers endpoint stores a malicious licensed domain that is executed unescaped in administrators' dashboard license-mismatch warnings.
Craft CMS versions from 5.0.0 up to but not including 5.11.4 have a session management vulnerability related to two-factor authentication (2FA). The flaw allows existing sessions to remain valid even when 2FA is enabled and permits disabling 2FA without requiring re-authentication. An attacker with a hijacked or stale session can maintain full account access and remove 2FA protections without needing the password, authenticator code, or recovery code.
Craft CMS versions from 5.0.0 up to but not including 5.11.4 contain a vulnerability due to an incomplete blocklist fix. This flaw allows attackers who have the ability to author entry type title formats to write arbitrary files to the web document root by abusing the non-sandboxed renderObjectTemplate() function with ZipArchive or XMLWriter classes. Successful exploitation can lead to remote code execution on the affected system.