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 from 2.0.0 before 2.2.18 contains a Twig injection vulnerability that allows media-only accounts and anonymous uploaders to execute Twig by placing delimiters in image titles, alt text, class, id, or file names. Attackers can combine injected Twig with the autoescape tag to serve script to every page visitor, including super admins, or expose unpublished page content.
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 before 2026.05.3 contains an account takeover vulnerability that allows invited users to complete other invitees' signups because batch invitations share one token across all recipients. Attackers holding a valid batch invite can submit another invitee's email with the shared non-expiring token to set its password and take over that account, including higher-role ones.
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 before 2026.08.0 contains an authorization bypass vulnerability in public shared-view endpoints that fetch records by primary key without applying the view's row filter. Anonymous share link holders can enumerate sequential primary keys on link, has-many, and attachment download endpoints to read excluded records' linked data and download their attachments.
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 before 2026.08.0 contains an information disclosure vulnerability that allows unauthenticated attackers to access attachments of filtered-out records through the shared view attachment-download endpoint. Attackers holding a public share link can enumerate sequential primary keys to obtain signed download paths for files on records the view's row filter excludes.
NocoDB before 2026.08.0 contains an authorization bypass in shared-view relation endpoints because parent-record lookups apply only the primary key, not the view's row filter. Anonymous share-link holders can enumerate auto-increment primary keys against the has-many, many-to-many, one-to-many and link-to-another-record routes to read linked records of filtered-out rows.
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 before 2026.08.0 contains an authorization bypass vulnerability that allows anonymous share link holders to access records excluded by a shared view's row filter, because the read-by-primary-key path ignores the view's filters. Attackers can request the public attachment-download or nested-link listing routes with a record id to mint signed download URLs for hidden files and read linked-record data.
NocoDB before 2026.08.0 contains an information disclosure vulnerability that allows unauthenticated shared-base link holders to read the base's stored plaintext password through the general base metadata endpoint. Attackers with a share link can query the base read or list responses in bases.controller.ts, which skip password stripping in sanitizeBase.ts, to obtain reusable plaintext passwords.