NocoDB before 2026.10.1 contains a consent phishing vulnerability that allows unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs through the unauthenticated dynamic client registration endpoint. Attackers can impersonate trusted applications on a consent screen lacking unverified-client warnings or redirect host display, obtaining tokens to read and write victim tables and records.
NocoDB from 0.301.4 before 2026.10.0 contains an information disclosure vulnerability that allows authenticated workspace viewers to read pending invitation tokens through the workspace member list. Attackers can redeem an exposed higher-privileged invitation token at signup to claim the invited account and escalate to roles such as workspace owner.
NocoDB before 2026.10.1 contains a credential exposure vulnerability in the connection-test endpoint that allows authorized integration users to redirect stored credentials by overriding connection host, port, and user fields. Attackers can point the test at a server they control to capture offline-crackable PostgreSQL md5 or MySQL handshakes and recover the stored database password.
NocoDB versions before 2026.10.1 have an authentication bypass vulnerability due to insufficient session expiration. Attackers holding revoked OAuth access tokens can reuse them via the session header to authenticate as first-party sessions. This bypasses token revocation, client existence checks, route allowlists, and granted resource scopes, enabling unauthorized profile modifications, storage uploads, and forced global sign-outs.
NocoDB from 2026.07.0 before 2026.10.0 contains an sql injection vulnerability that allows users with Creator role to inject SQL through unescaped backslashes in the DATETIME_FORMAT formula format argument on MySQL-backed bases. Attackers can place a backslash before a quote to terminate the DATE_FORMAT string literal and read any data reachable by the data source's database user, including tables outside the base.
NocoDB before 2026.10.1 contains a template injection vulnerability that allows authenticated Creator-role users to execute server-side JavaScript by supplying array-form property paths to Handlebars helpers in webhook templates. Attackers can bypass the string-only prototype guard to reach the function constructor, running operating-system commands with server privileges or exfiltrating process-internal values via outbound requests.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability due to predictable file paths for data exports. Unauthenticated attackers can reconstruct these paths using table and view metadata to download full data exports, including fields hidden from public views.
NocoDB before 2026.10.1 contains an incorrect authorization vulnerability that allows organization Creators to reach routes restricted to other roles because the aclFn middleware never enforced allowedRoles. Attackers can generate a super admin password reset link via org-users endpoints to take over the instance, or read and modify SSO client secrets.
NocoDB before 2026.10.1 contains a stored HTML injection vulnerability that allows authenticated users with record edit rights to inject forms, images, and styled overlays into rich text cells, which are sanitized only with DOMPurify's default policy. Attackers can place a page-sized spoofed sign-in form or remote image in a cell to harvest passwords and disclose viewer IP addresses in expanded records, gallery and kanban cards, and shared views.
NocoDB before 2026.10.0 contains an sql injection vulnerability that allows authenticated users with the Creator role to inject SQL by supplying a crafted formula parsed_tree during table creation. Attackers can set a malicious binary-expression operator that is interpolated into a knex.raw fragment, reading user and token tables and escalating to super administrator on SQLite installs.
NocoDB versions prior to 2026.10.1 contain a stored CSS injection vulnerability that allows authenticated users with Commenter or Editor roles to inject inline styles via single quotes in mention text. This injection can manipulate the user interface for other viewers by breaking out of the single-quoted data-id attribute in comments or rich text cells.
CVE-2026-130683 is a critical path traversal vulnerability in siyuan-note versions before 3.8.10. The application uses an incomplete deny-list for sensitive paths, omitting important shell initialization files and directories. Authenticated administrators can exploit this flaw by calling the /api/file/copyFile endpoint with an absolute path outside the workspace, allowing them to write malicious payloads that execute with user privileges upon the next shell or login. This vulnerability is fixed in version 3.8.10.
SiYuan before 3.8.10 persists a table block's caption attribute into IAL properties without HTML sanitization, causing stored cross-site scripting upon import or sync. Attackers can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context to achieve remote code execution.
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel.
SiYuan from 3.3.0 before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to inject HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. Attackers can share a crafted .sy.zip document whose rendering in the Electron desktop client with nodeIntegration enabled executes Node.js and host OS commands.
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to execute script by storing malicious Attribute View column names rendered unescaped in col.ts. Attackers can inject HTML via addAttributeViewKey, .sy.zip import, or sync, and when a victim adds or duplicates the column, insertAdjacentHTML runs JavaScript with Node.js privileges for desktop code execution.
SiYuan note-taking software versions before 3.8.10 contain 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 when a user opens the affected note or attribute panel in the desktop application. This vulnerability is critical and has been fixed in version 3.8.10.
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 access installation IDs and device tokens of other devices and modify installations to redirect push notifications.
The Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.10 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to create, modify, and delete entries in the site-wide global button-preset store, and inject arbitrary CSS rules into the generated plus-button-presets stylesheet served to all site visitors.
The Groundhogg plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_title' merge-tag of the [ghr] shortcode in versions up to, and including, 4.10 The post_title replacement is registered with 'nested' => true, so the nested branch of Replacements::do_replacement() returns the merge value through tackle_replacements() without passing it through escape_merge_tags()/escape_shortcodes(); the callback single_post() calls html_entity_decode(get_the_title(), ENT_QUOTES), converting the entity-encoded text that wp_filter_kses leaves intact on a Contributor's post title back into raw HTML, which is then emitted into the rendered post. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.