NocoDB versions prior to 2026.10.0 have an improper access control vulnerability that allows users with Creator roles to exploit internal database flags. By supplying is_meta and is_local flags, attackers can create sources or bases that expose sensitive tables containing user, token, and integration data. This enables unauthorized reading and modification of records, including user roles.
NocoDB versions before 2026.10.1 have a consent phishing vulnerability that permits unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs via an unauthenticated dynamic client registration endpoint. This flaw allows attackers to impersonate trusted applications on the consent screen without unverified-client warnings or redirect host display, enabling them to obtain tokens that can read and write victim tables and records.
NocoDB versions prior to 2026.10.0 have an information disclosure vulnerability that allows unauthenticated attackers to access hidden column data. By supplying comma-separated group-by column lists, attackers can bypass restrictions on shared view links and retrieve hidden values associated with individual rows.
NocoDB versions prior to 2026.10.1 contain an authentication bypass vulnerability that allows attackers holding revoked OAuth access tokens to authenticate as first-party sessions. This bypass enables attackers to circumvent token revocation, client existence checks, route allowlists, and granted resource scope validations. Exploitation can lead to unauthorized modification of victim profiles, uploading to storage, and forcing global sign-outs.
SiYuan versions before 3.8.10 contain a vulnerability where the table block's caption attribute is persisted into IAL properties without proper HTML sanitization. This flaw allows stored cross-site scripting (XSS) upon import or synchronization. An attacker can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context, potentially leading to remote code execution.
SiYuan versions prior to 3.8.10 have a stored cross-site scripting (XSS) vulnerability in the genAVValueHTML() function. This flaw allows attackers who can store Attribute View asset values to inject malicious scripts via an unescaped image src attribute. The injected script can include a double quote and an onerror handler that executes operating system commands through Node.js in the desktop application when a user opens the affected note or attribute panel.
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 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.
The Nexter Blocks plugin for WordPress contains an authorization bypass vulnerability in all versions up to and including 5.0.10. This flaw allows authenticated users with contributor-level access or higher to create, modify, and delete entries in the global button-preset store. Additionally, attackers can inject arbitrary CSS rules into a stylesheet served to all site visitors. The vulnerability does not impact confidentiality or availability but can affect the integrity of site content and styling.
The Groundhogg WordPress plugin up to version 4.10 is vulnerable to stored cross-site scripting (XSS) via the 'post_title' merge-tag in the [ghr] shortcode. This vulnerability allows authenticated users with Contributor-level access or higher to inject arbitrary scripts into pages, which execute when those pages are viewed. The issue arises because the post_title replacement bypasses proper escaping, and HTML entities are decoded back into raw HTML before rendering.
Apache Iggy server version 0.9.0 has a vulnerability where it generates a root password if started without IGGY_ROOT_USERNAME and IGGY_ROOT_PASSWORD environment variables and logs this password in the server log file. Users with read_servers permission can access these logs via the system snapshot command, allowing them to obtain the root password and gain root access. This issue is fixed in version 0.10.0, which does not generate a root password and restricts snapshot access to users with manage_servers permission.