Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain an information disclosure vulnerability. This flaw allows users with publisher or read-only user manager roles to access sensitive data such as password hashes, two-factor authentication secrets, and reset tokens. The vulnerability arises from unfiltered account serialization, enabling attackers to embed a Flex form for the user-accounts directory in a page or query the Flex API with admin.users.read permissions. Exploiting this can lead to obtaining super admin credentials and full account takeover.
Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have a vulnerability where page media files and rendered pages served with lazy sessions enabled include the visitor's session cookie and a shared-cacheable Cache-Control header. This allows shared caches like Apache mod_cache to store responses containing Set-Cookie headers. An attacker can exploit this by tricking a logged-in user to access a specially crafted media URL, then retrieve the cached response to obtain the user's session cookie and hijack their session.
A privilege escalation vulnerability exists in Grav versions from 2.0.0 up to but not including 2.2.18. This flaw allows user managers with certain permissions to escalate their privileges to super-admin by exploiting YAML merge key nesting in access maps. Specifically, attackers with admin.users.create or api.users.write permissions can submit specially crafted '<<' keys via API requests to bypass super-grant filtering and gain full control of the site.
A privilege escalation vulnerability exists in Grav versions from 2.0.0 up to but not including 2.2.18. This flaw allows user managers who have the admin.users.update permission to disable the super-granting group via the Flex user-groups form. By doing so, they can then reset the password of super admin accounts through the user-accounts form and gain unauthorized super admin access.
A remote code execution vulnerability exists in Grav CMS versions from 2.0.0 up to but not including 2.2.18. This flaw allows page editors to bypass the Twig sandbox by sending requests with a specific Host header, enabling attackers to write configuration YAML files that register an unsandboxed Twig namespace and execute shell commands as the web server user.
Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain a vulnerability involving insecure blueprint trust. This flaw allows publisher-level accounts to read sensitive secrets and execute arbitrary PHP code by manipulating blueprint files. Attackers can exploit features such as the import@ directive, specially named YAML media files, or form.flash_folder to leak password hashes, keys, or invoke static PHP methods for code execution.
A privilege escalation vulnerability exists in Grav versions from 2.0.0 up to but not including 2.2.18. This flaw allows user managers and Flex editors to manipulate client-controlled storage keys to overwrite, create, or delete user accounts. Exploitation methods include abusing the create form username, cross-type form flash replay, or __META storage key rename, potentially granting attackers super-admin privileges or enabling account deletion.
Grav CMS versions from 2.0.0 up to but not including 2.2.18 contain a remote code execution vulnerability. This flaw allows publishers to bypass the media action allowlist by using scoped method names in Markdown image URLs. Exploitation can lead to arbitrary file reading and execution of shell commands with the web server's privileges.
NocoDB versions prior to 2026.08.0 have an authorization bypass vulnerability in their public shared-view relation endpoints. These endpoints verify only the existence of a parent record but do not enforce the view's row filters. This allows unauthenticated attackers with access to a public share link to guess auto-incrementing IDs of filtered-out records and access their child records via various relation endpoints.
NocoDB versions prior to 2026.07.0 contain an SQL injection vulnerability affecting its MySQL and SQLite clients. Authenticated users with Creator or Owner roles can exploit this by supplying a crafted column precision value during column creation or update, which is inserted without numeric validation into data-definition statements. This allows execution of arbitrary SQL commands against the database.
NocoDB versions before 2026.10.0 have an insecure direct object reference (IDOR) vulnerability. Authenticated users with write access to attachment columns can exploit this flaw to obtain signed download URLs for attachments belonging to other bases by inserting foreign attachment paths into their own data rows. This allows reading of cross-base files even when secure attachment mode is enabled.
Grav CMS 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 Twig delimiters in image metadata fields such as titles, alt text, class, id, or file names. Exploitation can lead to script execution on pages viewed by any visitor, including super administrators, or unauthorized exposure of unpublished content.
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.