CVE-2026-82951 is a server-side request forgery (SSRF) vulnerability in Latvijas Valsts radio un televīzijas centrs (LVRTC) eParakstītājs 3.0 version 1.10.0-resolute. An unauthenticated remote attacker can exploit this by convincing a user to open a crafted signed eDOC file, causing HTTP GET requests from the user's workstation. The vulnerability involves automatic certificate validation that retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL and follows redirects without destination restrictions, enabling blind SSRF to internal network services. Additionally, loading local file URIs without restriction can cause unbounded memory buffering, leading to denial of service (OutOfMemoryError). The impact is higher in automated server verification pipelines. A fix is available in version 1.11.0.
Grav versions from 2.0.0 up to but not including 2.2.18 have a resource exhaustion vulnerability. Unauthenticated attackers can exploit this by sending HTTP requests with varying Host headers, causing the system to create multiple cached configurations and indexes. This can fill the disk space, leading to session, upload, and logging failures.
Grav from 2.0.0 before 2.2.18 contains a password reset poisoning vulnerability that allows anonymous attackers to redirect reset links by forging the CloudFront-Forwarded-Proto header. Attackers can send a forgot-password request with a crafted scheme value so the emailed reset link points to their host, capturing the token to take over accounts including super admins.
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 wildcard patterns in the UserCollection::count() method. Specifically, if the installation path contains brackets or backslashes, the account count incorrectly returns zero, enabling attackers to bypass authentication via specific API or admin registration endpoints.
Grav CMS versions before 1.7.53.7 and 2.x before 2.2.18 have a vulnerability where sensitive session cookies can be cached and served to unauthorized users when lazy sessions are enabled and a shared cache is used. This can allow attackers to hijack user sessions by exploiting cached responses containing session cookies.
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 versions from 2.0.0 up to but not including 2.2.18 contain a vulnerability in the blueprint trust mechanism that allows publisher accounts to read sensitive secrets and execute arbitrary PHP code. This is achieved by manipulating blueprint files via the import@ directive, specially named YAML media, or form.flash_folder. The vulnerability was fixed in version 2.2.18.
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 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.