CVE-2026-115934 is a critical SQL injection vulnerability in CraftCMS affecting versions 4.0.0 up to but not including 4.18.9, and 5.0.0 up to but not including 5.11.2. It allows unauthenticated attackers to perform stacked SQL queries via the craft.search front-end search feature on MySQL/MariaDB databases. This can lead to unauthorized read and write access to the application database, including privilege escalation to administrator by modifying user records. The vulnerability is fixed in versions 4.18.9 and 5.11.2. Temporary mitigation includes blocking front-end requests containing the attribute parameter in the query string.
CVE-2026-115938 is a high-severity vulnerability in Craft CMS that allows authenticated control panel users to exploit improper neutralization of special elements in the Twig template engine. The flaw enables bypassing sandbox restrictions via repeated single-segment property lookups, leading to leakage of the GeneralConfig::securityKey. This key can then be used to forge signed parameters, which are rendered unsandboxed, allowing invocation of native PHP callables. The vulnerability affects Craft CMS versions 4.0.0 up to but not including 4.18.9 and 5.0.0 up to but not including 5.11.2. Fixed versions are 4.18.9 and 5.11.2.
CVE-2026-115935 is a code injection vulnerability in CraftCMS affecting versions 4.0.0 up to but not including 4.18.9 and 5.0.0 up to but not including 5.11.2. It allows authenticated non-admin control panel users with accessCp permission to inject newline characters into the X-Craft-Plugin-Licenses header. This header value is written to the .env file without sanitization, enabling the attacker to insert a malicious CRAFT_SECURITY_KEY. Once loaded, this key allows forging of signed login redirects containing Twig system() callbacks, leading to code execution. This vulnerability is distinct from a previous issue that involved reading the existing key via a Twig sandbox bypass. A fix is available in versions 4.18.9 and 5.11.2.
Craft CMS versions 5.0.0 up to but not including 5.11.0 contain an authenticated remote code execution vulnerability in the Control Panel action app/render-components. Any authenticated user with basic Control Panel access can exploit this flaw by submitting specially crafted component classes and property overrides, leading to arbitrary Twig template code execution. This vulnerability allows execution of PHP functions such as system(), resulting in operating system command execution with the privileges of the web server process. The issue does not require admin privileges or access to sensitive settings or files.
CVE-2026-79987 is a high-severity vulnerability in Craft CMS that allows a remote, authenticated user with only the accessCp permission (non-admin) to execute operating system commands as the PHP web worker. This issue arises from unsafe reflection due to externally controlled input used to select classes or code. The vulnerability affects Craft CMS versions from 5.8.0 up to but not including 5.10.13.
Craft CMS versions before 5.10.12 contain a remote code execution vulnerability in the element-index endpoint that allows authenticated content editors to instantiate arbitrary classes through the criteria parameter. Attackers can inject a malicious class via criteria[withTransforms][0][class] that reaches ImageTransforms::normalizeTransform(), then use a PHP gadget chain with yii\rbac\PhpManager to execute code by pointing itemFile to a request log containing PHP payload in the User-Agent header.
Craft CMS GraphQL entry mutation resolvers (saveEntry, deleteEntry) read siteIddirectly from$argumentswithout passing throughArgumentManagerprepareArguments(), which is the function that enforces site-scope filtering via array_intersect against the GraphQL schema’s allowed sites. The query path (ElementResolverprepareElementQuery) correctly calls prepareArguments()`, so queries to unauthorized sites return empty. But mutations bypass this entirely — an attacker with a token scoped to Site A can create, modify, or delete entries in Site B by passing siteId in the mutations argument.
Craft CMS GraphQL entry mutation resolvers (saveEntry, deleteEntry) read siteIddirectly from$argumentswithout passing throughArgumentManagerprepareArguments(), which is the function that enforces site-scope filtering via array_intersect against the GraphQL schema’s allowed sites. The query path (ElementResolverprepareElementQuery) correctly calls prepareArguments()`, so queries to unauthorized sites return empty. But mutations bypass this entirely — an attacker with a token scoped to Site A can create, modify, or delete entries in Site B by passing siteId in the mutations argument.
The vulnerability allows any authenticated user to change their own password without providing the current password or having an active elevated session. It also allows the attacker to change other users’ passwords if the attacker’s account has Edit users permission (which doesn’t allow changing others’ passwords) and lacks Administrate users permission (which is required to change others’ passwords).
CVE-2026-79988 is a high-severity vulnerability in Craft CMS where the Twig sandbox mechanism is improperly configured, allowing dangerous Yii framework functionality. This misconfiguration enables authenticated remote code execution (RCE) similar to previously known issues. The affected versions include 4.0.0-RC1 and 5.0.0-RC1. No official patch or remediation guidance is currently available, and no known exploits are reported in the wild.
Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in the control panel element-search condition handling. The vulnerability arises due to a JSON cleanse bypass in condition.config, allowing Yii behavior/event configuration keys to be interpreted after decoding, which enables command execution as the PHP/web user.
Craft CMS versions before 5.10.8 contain an authentication bypass vulnerability in the elements/save action that allows authenticated users to change passwords without verification. Attackers with edit users permission can reset any user's password including administrators by exploiting the unprotected newPassword field in the User element save flow.
Craft CMS versions 4.0.0-RC1 through before 4.18.3 and 5.0.0-RC1 through before 5.10.7 contain a remote code execution vulnerability via the Twig sandbox escape. An authenticated user with control panel access can exploit the vulnerability by rendering a malicious Twig template that abuses the yii\base\Component arbitrary function-call gadget, enabling arbitrary code execution even when the Twig sandbox is enabled.
Craft CMS versions 4.0.0-RC1 before 4.18.2 and 5.0.0-RC1 before 5.10.6 contain a vulnerability where environment variables and secrets are interpolated into Twig templates even when sandboxing is enabled. An authenticated attacker with control panel access can exploit this to leak sensitive environment variables incrementally using a blind error-based technique. This can lead to session forgery, privilege escalation, and theft of credentials such as database, SMTP, API, or blob storage keys. The issue is fixed in versions 4.18.2 and 5.10.6.
Craft CMS versions 5.0.0-RC1 through 5.10.5 contain an authorization vulnerability allowing users with only viewCategories permission to modify the category structure. This occurs because the system incorrectly uses the view permission to authorize structural changes, enabling reordering and re-parenting of categories without proper save permission. Modifying category structure changes category URIs and can disrupt navigation menus. The issue is fixed in version 5.10.6.
Craft CMS versions 4.0.0-RC1 before 4.18.2 and 5.0.0-RC1 before 5.10.6 contain a theoretical path traversal weakness in the ensurePathIsContained function of the Local file system class. The vulnerability arises because path validation occurs before normalization, which may allow paths to resolve outside the intended directory. The vendor states the issue is not directly exploitable and no exploit scenarios have been found. The fix is recommended for hardening purposes.
Craft CMS versions 4.0.0-RC1 through before 4.18.2 and 5.0.0-RC1 through before 5.10.6 contain an arbitrary file read vulnerability. This occurs because the create() Twig function's class instantiation blocklist does not include SplFileObject, allowing an authenticated administrator with allowAdminChanges=true to instantiate SplFileObject in a non-sandboxed template context. This can lead to arbitrary files on the server, such as .env files containing sensitive credentials, being read and rendered in entry titles.
Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in the control panel element-search condition handling. The vulnerability arises because a JSON string in condition.config is not properly cleansed after decoding, allowing special Yii configuration keys to be interpreted and executed. An attacker with an authenticated control panel session and a valid CSRF token can exploit this to execute operating system commands as the PHP/web user.
Craft CMS versions from 4.0.0-RC1 before 4.18.2 and from 5.0.0-RC1 before 5.10.6 contain an authenticated remote code execution vulnerability in the control panel element-search condition handling. Craft cleanses the outer request-controlled condition array via Component::cleanseConfig(), but Conditions::createCondition() later decodes and merges the JSON string in condition.config without re-running cleanseConfig() on the decoded configuration. Because condition.config is a JSON string during the first cleanse, Yii special config keys such as 'as ...' and 'on ...' can be hidden inside it and, after JSON decoding, are interpreted by Yii as behavior/event configuration during FieldLayout object creation. An attacker with an authenticated control panel session (and a valid CSRF token) can exploit this to execute operating system commands as the PHP/web user.
Craft CMS passkey login functionality improperly handles WebAuthn assertions by accepting replayed requestOptions and failing to update the stored credential counter. This allows an attacker who captures a successful passkey login request body to replay it and create additional authenticated sessions for the victim user, effectively bypassing WebAuthn's replay protections and enabling account/session takeover.