NocoDB versions prior to 2026.08.0 have an information disclosure vulnerability that allows unauthenticated users with a shared-base link to access the base's stored plaintext password via the general base metadata endpoint. This occurs because the password is not stripped from the base read or list responses, enabling attackers to obtain reusable plaintext passwords.
NocoDB versions prior to 2026.04.1 contain a vulnerability where reset password tokens and their expiration timestamps are not cleared after a password change. This flaw allows attackers who possess a still-valid reset link, possibly obtained from prior mailbox access, to reuse the link to reset the password again and regain account control.
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows authenticated Creator or Editor users to execute script by injecting markup into fields rendered through URL() formulas. The canvas grid renderer assigns unsanitized formula output to innerHTML, letting attackers steal session tokens from localStorage and take over accounts of users viewing the table.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability. Unauthenticated attackers can submit email addresses to the signup endpoint and observe response differences to determine if an email is registered or has a pending Enterprise invitation, even when signup is invite-only. This vulnerability was fixed in version 2026.10.1.
NocoDB versions prior to 2026.08.0 contain an SQL injection vulnerability that allows authenticated users with Creator or Owner roles to execute database functions by using zero-argument function calls as column default values. This can lead to disclosure of sensitive database information such as server addresses, role names, and engine details.
NocoDB before 2026.08.1 contains an authorization bypass vulnerability that allows authenticated Creators to access another tenant's external database by reusing a victim source id when adding a source. Because NcConnectionMgrv2 caches connections by bare source id, attackers can reflect the victim's cached database schema and read, update, and insert records through their own base models.
NocoDB versions before 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to identify pending invitees by observing distinct sign-in error messages. This occurs because the authentication service skips password comparison for saltless invited accounts, confirming the existence of an account associated with the email address.
NocoDB versions prior to 2026.09.0 contain an authorization bypass vulnerability that allows authenticated users with Viewer access on one base to access metadata of another base by supplying a manipulated MCP token id in the query string. This flaw enables unauthorized reading of sensitive information such as table lists and member email addresses. The vulnerability is fixed in version 2026.09.0.
NocoDB versions prior to 2026.09.0 have a missing authorization vulnerability in the job status polling endpoint. This flaw allows unauthenticated attackers who know a job ID to access buffered status messages and completion payloads. Sensitive information such as signed export download URLs or new base identifiers may be exposed. The vulnerability is fixed in version 2026.09.0.
NocoDB versions before 2026.09.0 have a server-side template injection vulnerability that allows authenticated users with Creator or Owner roles to execute arbitrary JavaScript. This occurs through abuse of Handlebars webhook helpers, enabling attackers to reach the Function constructor and execute operating system commands.
NocoDB before 2026.09.0 contains an improper authorization vulnerability that allows workspace Creator users to read plaintext notification webhook URLs by querying the webhook plugin listing endpoint. Attackers can replay exposed Slack, Teams, Discord and Mattermost webhook URLs directly against messaging providers to post arbitrary messages into organization chat channels.
NocoDB versions prior to 2026.09.0 contain a critical SQL injection vulnerability. Authenticated users with Creator or Owner roles can inject raw SQL through a crafted formula that bypasses SQLite metadata protections. This flaw allows escalation to super administrator privileges or execution of OS commands on external PostgreSQL hosts. The vulnerability is fixed in version 2026.09.0.
NocoDB versions from 0.301.4 up to but not including 2026.10.1 have a vulnerability where the nc_token session cookie is set without the Secure attribute in HTTPS sessions. This allows network attackers to potentially capture the session token by observing or inducing plain HTTP requests to HTTPS instances, enabling session impersonation until the token expires. The issue is fixed in version 2026.10.1.
NocoDB before 2026.10.0 contains an improper access control vulnerability that allows Creator-role users to attach NocoDB's internal database by supplying is_meta and is_local flags. Attackers can create sources or bases with these flags to expose user, token and integration tables, then read and modify records including user roles.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated users holding shared view links to access hidden columns. By exploiting the public group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and existence. This vulnerability is fixed in version 2026.10.1.
NocoDB versions before 2026.10.0 contain an account takeover vulnerability. Users with the base creator role can exploit the baseUserInviteResend function to generate a new invite token, read it from the base member list, and reset the victim's password via signup. This allows attackers to hijack accounts, including owner or super admin accounts.
NocoDB versions prior to 2026.10.0 have an information disclosure vulnerability that allows unauthenticated attackers to access hidden column data. This occurs when attackers supply comma-separated group-by column lists, enabling them to bypass restrictions on shared view links and retrieve hidden values tied to individual rows.
NocoDB versions before 2026.10.1 have an SQL injection vulnerability due to improper escaping of backslashes in select-field option titles embedded in MySQL or MariaDB enum/set column definitions. This flaw allows a base creator or owner to manipulate option titles to inject malicious ALTER TABLE commands, potentially modifying database schema elements such as columns and indexes.
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 versions from 0.301.4 up to but not including 2026.10.0 contain an information disclosure vulnerability. Authenticated workspace viewers can access pending invitation tokens via the workspace member list. These tokens can be redeemed by attackers to claim invited accounts and escalate privileges to roles such as workspace owner. The vulnerability is rated high severity with a CVSS score of 7.1. A fix is available in version 2026.10.0.