Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged page editor
-
DeliveryLocate form with email-action parameters
-
ExploitInject Twig payload into subject, body, to, or from field
-
ExecutionSubmit form to trigger server-side Twig evaluation
-
PersistUnsandboxed find filter executes OS command
-
ImpactArbitrary code runs as web server process
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V1 - Encoding and Sanitization Template injection prevention
|
| Exploitation Conditions | Exploitation requires a valid Grav CMS page editor account - the minimum authenticated role capable of configuring or submitting forms with email-action parameters. The target installation must be running a Grav CMS version prior to 2.0.13, and at least one form must have email-action configured with parameters (subject, body, to, or from) that are rendered through the unsandboxed Twig |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) characterizes this as network-reachable with low attack complexity, requiring only low-privileged access and no user interaction - consistent with any authenticated page editor. High impact across VC/VI/VA confirms full system compromise potential. No EPSS score was supplied, preventing probabilistic exploitation likelihood assessment; this gap should be noted by defenders. The CVE is not listed in CISA KEV and no POC has been confirmed, meaning active exploitation is not verified. However, SSTI via Twig is a well-catalogued attack class with widely published technique libraries, substantially lowering the bar for a motivated attacker once the affected endpoint is identified. The PR:L requirement is the primary real-world limiting factor: exploitation is constrained to authenticated page editors, meaning sites with tightly controlled or trusted-only editor roles face materially lower risk than those permitting broad or self-service editor registration. |
| Exploit ScenarioDerived | A threat actor with a valid Grav page editor account navigates to a form configured with email-action and injects a Twig payload such as |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 14, 2026
Server-side template injection in Grav CMS before 2.0.13 allows low-privileged page editors to execute arbitrary operating-system commands via the Twig templating engine. Attackers exploit the unsandboxed find filter in email-action form parameters - injecting Twig payloads into subject, body, to, or from fields - which are evaluated server-side upon form submission, yielding full RCE. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 score of 8.7 (VC:H/VI:H/VA:H) reflects full-compromise potential on the vulnerable system for any actor holding a page editor account.
RemediationAI
Upgrade to Grav CMS 2.0.13 or later, the vendor-released patch confirmed by GitHub Security Advisory GHSA-xx48-97m4-h7qm (https://github.com/getgrav/grav/security/advisories/GHSA-xx48-97m4-h7qm). If immediate patching is blocked, apply the following compensating controls as interim measures: restrict the page editor role exclusively to fully trusted internal users and revoke it from any externally-facing or self-registered accounts - this eliminates the PR:L attack surface but may disrupt legitimate content workflows and should be communicated to affected teams. Additionally, consider temporarily disabling email-action form processing site-wide by removing or commenting out email-action handlers in form configurations, which eliminates the vulnerable code path at the cost of disabling form-triggered email functionality. Audit existing page editor accounts for unauthorized or suspicious additions before patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Grav is a flat-file PHP CMS that uses the Twig templating engine for content rendering. CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine) identifies the root cause class: user-supplied data is rendered through a Twig evaluation context that lacks sandboxing. Specifically, the email-action handler in Grav's form plugin accepts template expressions in fields such as subject, body, to, and from, and processes them via the find filter outside Twig's sandbox restrictions. This allows arbitrary PHP execution, including shell command invocation. The CPE string cpe:2.3:a:getgrav:grav:*:*:*:*:*:*:*:* covers all Grav versions prior to the patched release, indicating the flaw is not limited to a specific minor branch.
Know when Grav gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Network-reachable form submission, low complexity; PR:L for required editor account; S:C because OS-level command execution breaks out of the CMS application boundary.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
Grav CMS before 2.0.13 contains a server-side template injection vulnerability in email-action parameters that allows low-privileged page editors to execute arbitrary operating-system commands. Attackers can inject Twig payloads using the unsandboxed find filter in email subject, body, to, or from fields to achieve remote code execution when forms are submitted.
Executive ViewAI
Grav CMS versions before 2.0.13 are vulnerable to template injection attacks that allow page editors to execute arbitrary system commands and achieve complete server compromise, potentially exposing sensitive data, disrupting services, or enabling lateral movement into internal networks. No public exploit code identified at time of analysis, but the vulnerability poses critical risk for any organization where page editor accounts are provisioned or could be compromised by internal or external threats. Organizations running vulnerable Grav CMS versions must treat this as a priority mitigation to prevent total infrastructure compromise.
No vendor-released patch identified at time of analysis. Interim mitigations include: (1) restrict page editor account access to fully-vetted, essential personnel only; (2) implement web application firewall rules to block Twig template injection attempts in Grav CMS form submissions; (3) enable audit logging for all page editor account activities and conduct daily log reviews for suspicious command execution; (4) network-segment Grav CMS systems from critical internal infrastructure; (5) establish rapid incident response procedures to immediately isolate systems upon detection of exploitation attempts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Server-side template injection (SSTI) in Grav (getgrav/grav) prior to 1.8.0-beta.27 allows an authenticated attacker hol
Broken access control in Grav CMS (CWE-285) before 1.8.0-beta.27 lets an authenticated editor-level user escalate their
A Remote Code Execution (RCE) vulnerability in Grav CMS v1.7.48 allows an authenticated admin to upload a malicious plug
Grav is a file-based Web platform. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low a
GravCMS 1.10.7 allows unauthenticated remote attackers to write arbitrary YAML configuration files, leading to full serv
Remote code execution in Grav CMS 2.0.4 (fixed in 2.0.7) lets an authenticated user holding the admin.pages or api.pages
Remote code execution in Grav CMS before 2.0.15 allows attackers holding page-edit or blueprint-config privileges to wri
Vertical privilege escalation in Grav CMS before 2.0.14 lets a delegated administrator holding only the admin.users perm
Stored cross-site scripting in Grav CMS before 2.0.15 lets authenticated editors smuggle JavaScript event handlers past
Server-side request forgery (SSRF) in Grav CMS versions prior to 1.7.49.5 allows remote authenticated attackers to make
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, Grav CMS is vulnerable to a Server-Side Template Injection (S
Remote code execution in Grav CMS before 2.0.13 allows authenticated low-privilege users to plant and execute arbitrary
EUVD-2026-58641
GHSA-4jrc-qc5x-3wrr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB