CVE-2025-66299: getgrav grav · Code Injection
Affects getgrav gravSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 1.8.0 : patch getgrav grav soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubgetgrav/gravpkg:github/getgrav/gravOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Upgrade Grav CMS to version 1.8.0-beta.27 or later immediately to apply the official patch that fixes the vulnerability. 2. Restrict editor permissions strictly to trusted personnel, minimizing the number of users who can exploit this vulnerability. 3. Implement strong authentication mechanisms (e.g., multi-factor authentication) for editor accounts to reduce the risk of credential compromise. 4. Monitor web server and application logs for unusual Twig template activity or unauthorized code execution attempts. 5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious template injection patterns targeting Twig. 6. Conduct regular security audits and code reviews of custom Grav templates to ensure no unsafe Twig directives are present. 7. Isolate Grav CMS instances in segmented network zones to limit lateral movement if compromise occurs. 8. Educate content editors about the risks of uploading or editing templates and enforce strict content validation policies.
Description
Grav is a file-based Web platform. Prior to 1.8.0-beta.27, Grav CMS is vulnerable to a Server-Side Template Injection (SSTI) that allows any authenticated user with editor permissions to execute arbitrary code on the remote server, bypassing the existing security sandbox. Since the security sandbox does not fully protect the Twig object, it is possible to interact with it (e.g., call methods, read/write attributes) through maliciously crafted Twig template directives injected into a web page. This allows an authenticated editor to add arbitrary functions to the Twig attribute system.twig.safe_filters, effectively bypassing the Grav CMS sandbox. This vulnerability is fixed in 1.8.0-beta.27.