# CVE-2026-72827: Grav CMS before 2.0.13 Remote Code Execution via Twig

> Low-privileged page editors can execute arbitrary OS commands via Twig injection in email-action parameters, risking full server compromise.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-4jrc-qc5x-3wrr, GHSA-xx48-97m4-h7qm

## What is CVE-2026-72827?

CVE-2026-72827 is a high-severity code injection vulnerability in getgrav grav, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-72827?


## How do I fix CVE-2026-72827?

No fix has been published for CVE-2026-72827 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72827 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72827 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72827 and fix it if it is affected.

What it is: CVE-2026-72827 is a high-severity code injection vulnerability in getgrav grav, published on 14 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72827 exists.

Affected product: getgrav grav. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72827/ (Markdown: https://insights.sbomify.com/CVE-2026-72827/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72827
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72827
- OSV: https://osv.dev/vulnerability/CVE-2026-72827

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72827/
Summaries are generated and may contain mistakes; the official description above is the record.