Grav versions from 2.0.0 up to but not including 2.2.18 contain a privilege escalation vulnerability that allows user managers and Flex editors to manipulate account data by supplying user-controlled storage keys. This can lead to unauthorized creation, modification, or deletion of accounts, including gaining super-admin privileges. The vulnerability is fixed in version 2.2.18.
Grav versions from 2.0.0 up to but not including 2.2.18 contain a privilege escalation vulnerability. This flaw allows user managers with certain permissions to escalate their privileges to super-admin by exploiting improper neutralization of special YAML elements. Specifically, attackers with admin.users.create or api.users.write permissions can submit YAML payloads containing merge keys ('<<') via API requests to bypass super-grant filtering and gain full site control. The vulnerability is fixed in version 2.2.18.
Grav versions from 2.0.0 up to but not including 2.2.18 contain a stored cross-site scripting (XSS) vulnerability. This flaw allows users with media upload permissions to bypass the upload sanitizer by uploading crafted SVG files or certain XML/XHTML files. When administrators access the raw file URL, malicious scripts can execute. The vulnerability is fixed in version 2.2.18.
Grav versions from 2.0.0 up to but not including 2.2.18 contain a critical Twig injection vulnerability. This flaw allows media-only accounts and anonymous uploaders to execute arbitrary Twig code by embedding delimiters in image metadata such as titles, alt text, class, id, or file names. Exploitation can lead to script execution on pages viewed by all visitors, including super admins, and may expose unpublished page content. The vulnerability is fixed in Grav version 2.2.18.
Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows publishers to bypass the media action allowlist using scoped method names in Markdown image URLs. Attackers can chain actions like self::addMetaFile into static calls such as Process::fromShellCommandline to read files and run shell commands as the web server user.
Traefik from 2.11.58 before 2.11.61 contains a resource leak vulnerability that allows unauthenticated attackers to exhaust resources by sending Authorization headers with NTLM or Negotiate schemes. Attackers can open many short-lived connections that each allocate a dedicated backend transport never released, exhausting memory, file descriptors and backend connections.
Grav versions from 2.0.0 up to but not including 2.2.18 contain a critical authorization bypass vulnerability. This flaw allows attackers to overwrite pages that their per-page permissions should deny by exploiting FolderStorage key delimiter collisions and PageStorage folder reconstruction. Specifically, attackers can rename folders with certain patterns or save pages with unusual prefix widths via the front-end Flex pages form, enabling replacement of protected content and permissions. The vulnerability is fixed in Grav version 2.2.18.
NocoDB versions before 2026.05.3 have a vulnerability in the password recovery mechanism for invited users. The batch invitation system uses a single shared, non-expiring token for all invitees, allowing an attacker with a valid batch invite to set the password of any other invitee by submitting their email with the shared token. This flaw enables account takeover, including accounts with higher roles.
NocoDB versions before 2026.10.1 have an authentication bypass vulnerability where OAuth tokens signed with the instance JWT secret can be used to gain full user session privileges. This allows attackers with a narrowly scoped OAuth token to escalate their access by presenting the token to various authentication mechanisms within NocoDB.
NocoDB before 2026.08.0 contains a stored cross-site scripting vulnerability that allows any authenticated user to register OAuth clients with javascript: redirect URIs. Attackers can send a consent link to a signed-in victim so either consent button runs script in the NocoDB origin, stealing the session token for account takeover.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in their public shared-view relation endpoints. The flaw allows unauthenticated attackers with a public share link to access child records of filtered-out parent records by supplying guessable auto-incrementing IDs. This bypass occurs because the endpoints verify the existence of a parent record but do not enforce the view's row filters.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in public shared-view endpoints. This flaw allows anonymous users holding share links to enumerate sequential primary keys and access records that should be excluded by row filters, including linked data and attachments. The issue is fixed in version 2026.08.0.
NocoDB versions before 2026.07.0 have an SQL injection vulnerability in their MySQL and SQLite clients. Authenticated users with Creator or Owner roles can exploit this by supplying a crafted precision value when creating or updating a column, allowing execution of arbitrary SQL commands against the database.
NocoDB versions prior to 2026.10.0 contain an authorization bypass vulnerability that allows authenticated users with write access to attachment columns to obtain signed download URLs for attachments belonging to other bases. This occurs due to insecure direct object references via user-controlled foreign attachment paths, enabling cross-base file access despite secure attachment mode.
NocoDB before 2026.08.0 contains a server-side request forgery vulnerability that allows authenticated base Editors to make backend HTTP requests by supplying arbitrary URLs to the integration remote fetch operation. Attackers can control the method, headers, and body to reach internal APIs, loopback services, and cloud metadata endpoints, reading responses and echoed decrypted integration secrets.
NocoDB versions before 2026.08.0 have an information disclosure vulnerability that allows unauthenticated attackers to access attachments of records excluded by view filters via the shared view attachment-download endpoint. Attackers with a public share link can enumerate sequential primary keys to retrieve signed download paths for files on filtered-out records.
NocoDB versions before 2026.08.0 have an authorization bypass vulnerability in shared-view relation endpoints. The flaw arises because parent-record lookups use only the primary key without applying the view's row filter. This allows anonymous users with share links to enumerate auto-increment primary keys and access linked records that should be filtered out.
NocoDB versions from 2026.06.2 up to but not including 2026.08.0 contain an authorization bypass vulnerability. Authenticated users with base Editor privileges can exploit this flaw to write to data sources that are intended to be read-only by abusing the internal batch endpoint. This allows modification or destruction of records in read-only tables by referencing a writable decoy table in batch operations. The vulnerability is fixed in version 2026.08.0.
NocoDB before 2026.08.0 contains an insecure direct object reference vulnerability that allows unauthenticated attackers to access records hidden by a shared view's row filter by supplying arbitrary primary keys. Attackers with the share link can request attachment downloads and many-to-many or has-many link listings for excluded records to obtain their attachment files and linked record identities.
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability that allows anonymous users with share links to access records that should be restricted by row filters in shared views. This occurs because the read-by-primary-key access path does not enforce these filters. Exploitation enables attackers to generate signed download URLs for hidden files and access linked-record data via specific routes.