# CVE-2026-75574: Grav before 4.2.2 Remote Code Execution via Email Twig

> Authenticated users with page write permissions can execute arbitrary OS commands via unsandboxed Twig templates in the Grav Email plugin.

- **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:** 25 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-3625-697m-q29v

## What is CVE-2026-75574?

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

### Official description

The Grav Email plugin (getgrav/grav-plugin-email) before 4.2.2 renders page-editor-controlled Email action parameters as unsandboxed Twig templates. An authenticated remote user with only api.access and api.pages.write permissions can place a Twig expression in header.form.process.email.body, publish the page, and submit the form to execute an arbitrary operating-system command as the account running PHP.

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

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


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

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

## Is CVE-2026-75574 being exploited?

There is no known exploitation of CVE-2026-75574 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75574 is a high-severity code injection vulnerability in getgrav grav, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75574 in the wild and no public exploit code.

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-75574/ (Markdown: https://insights.sbomify.com/CVE-2026-75574/index.md)
```

## Sources

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

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