Grav from 2.0.0 before 2.2.18 contains a remote code execution vulnerability that allows page editors to escape the Twig sandbox by sending requests with a Host: pages header. Attackers can write configuration YAML through page folders and media .meta.yaml sidecars to register an unsandboxed Twig namespace and run shell commands as the web server user.
Grav versions from 2.0.0 up to but not including 2.2.18 have an access control bypass vulnerability. This flaw allows anonymous users to read protected pages due to shared page cache keys between admin and site scopes. The issue arises when the API plugin rebuilds the page index without enforcing frontmatter.yaml access rules, temporarily exposing members-only content until the cache is refreshed. The vulnerability is rated high severity with a CVSS 4.0 score of 8.2. A fix is available in version 2.2.18.
Grav from 2.0.0 before 2.2.18 contains an insecure blueprint trust vulnerability that allows publisher accounts to read secrets and execute PHP by planting or selecting attacker-controlled blueprint files. Attackers can abuse the import@ directive, uploaded YAML media named as the page template, or form.flash_folder to leak password hashes and keys or invoke static PHP methods for code execution.
A vulnerability in Grav versions 2.0.0 through before 2.2.18 allows authenticated users with only list access to delete all user accounts by exploiting unsafe reflection in the Flex API. This occurs because certain field names are resolved by calling public methods without permission checks, enabling a crafted request to invoke the delete method. The flaw is fixed in version 2.2.18.
Grav versions from 2.0.0 up to but not including 2.2.18 contain a vulnerability in the Twig sandbox that allows unauthorized reading of any server file. This is achieved by abusing allowlisted functions and page accessor setters to expose sensitive information such as private keys and API signing secrets. Exploitation could enable forging of super-admin API tokens. The vulnerability is rated high severity with a CVSS score of 8.7 and was fixed in version 2.2.18.
Grav from 2.0.0 before 2.2.18 contains an information disclosure vulnerability that allows publishers and read-only user managers to read password hashes, 2FA secrets and reset tokens through unfiltered account serialization. Attackers can embed a Flex form for the user-accounts directory in a page or query the Flex API with admin.users.read to obtain super admin credentials and take over the account.
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 the admin.users.update permission to disable the super-granting group by setting its enabled field to false via the Flex user-groups form. Subsequently, the attacker can reset a super admin's password through the user-accounts form and gain super admin access. The vulnerability is fixed in Grav version 2.2.18.
Grav from 2.0.0 before 2.2.18 contains a privilege escalation vulnerability that allows user managers and Flex editors to overwrite, create, or delete accounts by supplying client-controlled storage keys. Attackers can abuse the create form username, cross-type form flash replay, or __META storage key rename to gain super-admin accounts or delete account files.
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.