NocoDB versions prior to 2026.05.3 have an account takeover vulnerability due to batch invitations sharing a single non-expiring token. This flaw allows an attacker with a valid batch invite token to complete the signup process for other invitees by submitting their email and setting their password, potentially taking over accounts with higher privileges.
NocoDB versions prior to 2026.08.0 have an information disclosure vulnerability that allows unauthenticated attackers to access attachments of records excluded by view filters. Attackers with a public share link can enumerate sequential primary keys to retrieve signed download URLs for files attached to filtered-out records.
Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain an authorization bypass vulnerability. This flaw allows users with publisher-level permissions to overwrite pages that their per-page permissions should deny. The vulnerability arises from abusing FolderStorage key delimiter collisions and PageStorage folder reconstruction, enabling attackers to rename folders or save pages with unusual prefixes via the front-end Flex pages form. This results in unauthorized replacement of protected content and permissions within the protected subtree.
NocoDB versions before 2026.08.0 have a stored cross-site scripting (XSS) vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. This flaw enables attackers to craft consent links that, when clicked by signed-in users, execute malicious scripts in the NocoDB origin, potentially stealing session tokens and leading to account takeover.
Traefik versions from 2.11.58 up to but not including 2.11.61 contain a resource leak vulnerability. This flaw allows unauthenticated attackers to exhaust system resources by sending Authorization headers using NTLM or Negotiate schemes. Each malicious connection allocates backend transport resources that are not released, leading to exhaustion of memory, file descriptors, and backend connections.
NocoDB versions prior to 2026.08.0 have a server-side request forgery (SSRF) vulnerability that allows authenticated users with base Editor privileges to make arbitrary backend HTTP requests. This flaw enables attackers to control HTTP method, headers, and body to access internal APIs, loopback services, and cloud metadata endpoints, potentially exposing sensitive decrypted integration secrets.
NocoDB versions prior to 2026.10.1 have an authentication bypass vulnerability. This flaw allows attackers holding OAuth tokens, which are signed with the instance JWT secret, to escalate their privileges and act as full authenticated sessions. By presenting a narrowly scoped OAuth token to various authentication mechanisms, attackers can gain the full privileges of the granting user.
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability in their public shared-view endpoints. This flaw allows anonymous users with a share link to enumerate sequential primary keys and access records that should be filtered out by the view's row filter. Consequently, unauthorized users can read linked data from excluded records and download attachments they should not have access to.
A stored cross-site scripting (XSS) vulnerability exists in Grav versions from 2.0.0 up to but not including 2.2.18. This flaw allows users with media upload permissions to bypass the upload sanitizer by uploading crafted SVG files with inner extensions or unblocked XML/XHTML files. When administrators access the raw file URL, malicious scripts can execute. The vulnerability has a medium severity rating with a CVSS score of 5.4.
NocoDB versions before 2026.08.0 have an SQL injection vulnerability that allows authenticated users with Creator or Owner roles to execute database functions by using zero-argument function calls as default column values. This can lead to disclosure of sensitive database information such as server addresses, role names, and engine details.
NocoDB versions from 2026.06.2 up to but not including 2026.08.0 contain an authorization bypass vulnerability. This flaw allows authenticated users with base Editor privileges to write to data sources that are intended to be read-only. The vulnerability is exploited by abusing the internal batch endpoint, where an attacker can specify a writable decoy table and target a read-only source table in sub-operations such as dataUpdate, dataInsert, or dataDelete to modify or delete records.
NocoDB versions prior to 2026.08.0 have a stored cross-site scripting (XSS) vulnerability. Authenticated users with Creator or Editor roles can inject malicious markup into fields rendered via URL() formulas. This vulnerability allows execution of arbitrary scripts in the context of other users viewing the affected tables, potentially leading to session token theft from localStorage and account takeover.
NocoDB versions before 2026.04.1 do not clear the reset_password_token and reset_password_expires fields after a password change. This flaw allows previously issued password reset links to remain valid, enabling attackers who have access to such links to reset the password again and regain account control.
NocoDB versions prior to 2026.08.0 have an information disclosure vulnerability that allows unauthenticated users holding 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 metadata in certain API responses, enabling attackers with a share link to retrieve reusable plaintext passwords.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability. This flaw allows anonymous users holding share links to access records that should be restricted by a shared view's row filter. The vulnerability arises because the read-by-primary-key access path does not enforce these filters. Attackers can exploit this by requesting certain routes with record IDs to generate signed download URLs for hidden files and access linked record data.
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability in shared-view relation endpoints. This occurs because parent-record lookups rely solely on the primary key without applying the view's row filter. As a result, anonymous users with share links can enumerate auto-increment primary keys through various relation routes to access linked records that should be filtered out.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to determine pending invitees by observing distinct sign-in error messages. This occurs because the validateUser function skips password checks for saltless invited accounts, enabling attackers to confirm the existence of an email address associated with an account.
NocoDB versions prior to 2026.10.1 have a user enumeration vulnerability that allows unauthenticated attackers to distinguish registered email addresses by analyzing different responses from the sign-up endpoint. This includes identifying existing accounts and pending Enterprise invitations, even when sign-up is restricted to invite-only.
NocoDB versions prior to 2026.08.0 have an insecure direct object reference (IDOR) vulnerability. This flaw allows unauthenticated attackers to bypass shared view row filters by supplying arbitrary primary keys, accessing records that should be hidden. Attackers with a share link can also download attachments and enumerate linked records for excluded data.
NocoDB versions prior to 2026.08.1 contain an authorization bypass vulnerability that allows authenticated users with Creator privileges to access external databases of other tenants. This occurs due to connection caching by source ID, enabling attackers to reuse victim source IDs to access and manipulate another tenant's data.