Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have an authentication bypass vulnerability. This flaw allows anonymous users to create or overwrite super-admin accounts due to improper handling of user account counts when the installation path contains brackets or backslashes. The vulnerability arises because UserCollection::count() uses an unescaped glob() pattern, causing the account count to return zero incorrectly. Attackers can exploit this by sending requests to the setup authentication API or the classic admin registration form.
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.
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.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.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.
NocoDB versions from 0.301.4 up to but not including 2026.10.1 have a vulnerability where the nc_token session cookie is set via script in the Enterprise useGlobal composable without the Secure attribute. This omission allows attackers positioned on the network to capture the session token by observing or inducing plain-HTTP requests to HTTPS instances, enabling session impersonation until the token expires.
NocoDB versions prior to 2026.10.1 have a credential exposure vulnerability in the connection-test endpoint. Authorized integration users can manipulate connection parameters to redirect stored credentials to an attacker-controlled server. This allows attackers to capture PostgreSQL md5 or MySQL handshake data, which can be cracked offline to recover database passwords.
NocoDB versions prior to 2026.10.1 have an information disclosure vulnerability that permits unauthenticated users holding shared view links to access hidden column data. By exploiting the group-by endpoint with specific parameters, attackers can reveal hidden column values, counts, and confirm the existence of such columns.
NocoDB versions before 2026.10.1 have a consent phishing vulnerability that permits unauthenticated attackers to register OAuth clients with arbitrary HTTPS redirect URIs via an unauthenticated dynamic client registration endpoint. This flaw allows attackers to impersonate trusted applications on the consent screen without unverified-client warnings or redirect host display, enabling them to obtain tokens that can read and write victim tables and records.
NocoDB versions prior to 2026.10.1 contain an authentication bypass vulnerability that allows attackers holding revoked OAuth access tokens to authenticate as first-party sessions. This bypass enables attackers to circumvent token revocation, client existence checks, route allowlists, and granted resource scope validations. Exploitation can lead to unauthorized modification of victim profiles, uploading to storage, and forcing global sign-outs.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated attackers to download data exports by reconstructing predictable file paths. Attackers can derive these paths using table id, base, table and view titles, and export time, enabling access to full exports including fields hidden from public shared views.
NocoDB versions from 0.253.0 up to but not including 2026.09.1 contain an authorization vulnerability in the baseUserDelete function. This flaw allows users with the Creator role to remove Owners, who have higher privileges, due to incorrect role power comparison logic. The vulnerability arises because the function getProjectRolePower returns -1 for the target Owner, which does not block the deletion request as intended. The issue has a low CVSS score of 2.7 and does not impact confidentiality or availability but can cause integrity loss by unauthorized user removal.
NocoDB versions prior to 2026.10.1 contain a stored HTML injection vulnerability that permits authenticated users with record edit rights to inject malicious HTML content into rich text cells. The vulnerability arises because the sanitization relies solely on DOMPurify's default policy, which can be bypassed to insert forms, images, and styled overlays. Exploitation can lead to attackers embedding spoofed sign-in forms or remote images that harvest passwords and disclose viewer IP addresses in various views such as expanded records, gallery, kanban cards, and shared views.
A null pointer dereference vulnerability exists in ImageMagick versions before 7.1.2-35. This flaw can be triggered by using the -subimage option on a single-image list, causing the process to crash and resulting in a denial of service condition.
ImageMagick versions before 7.1.2-35 have a heap buffer over-read vulnerability in the processing of BGRO image data. This flaw allows attackers to read memory beyond the allocated buffer, potentially leaking adjacent heap contents or causing application crashes. The vulnerability requires attackers to supply crafted BGRO data for exploitation.
ImageMagick versions before 7.1.2-35 have a double free vulnerability triggered by using the DPC compare metric. This flaw allows attackers to cause an invalid memory free, leading to memory corruption and application crashes resulting in denial of service.
ImageMagick versions before 7.1.2-35 have a heap buffer overflow vulnerability that can be triggered by processing specially crafted images using the magick stream operation. This vulnerability allows attackers to write beyond allocated heap memory, potentially causing application crashes.
ImageMagick versions before 7.1.2-35 have a policy bypass vulnerability due to a missing policy check when reading XMP profiles. This flaw allows attackers to supply crafted images with malicious XMP profiles that evade resource limits, leading to excessive memory usage and potential denial of service.
ImageMagick versions before 7.1.2-35 have a use after free vulnerability in the EXR image decoder. This flaw occurs when a specific memory allocation fails, allowing crafted EXR images processed under memory pressure to trigger the vulnerability. The impact is limited to causing application crashes or memory corruption without compromising confidentiality or integrity.
ImageMagick versions before 7.1.2-35 have a heap buffer over-read vulnerability in the TIFF decoder. This flaw allows attackers to supply a crafted TIFF image that can cause heap memory corruption during encoding in certain output formats. The vulnerability has a medium severity rating with a CVSS score of 4.4.