# CVE-2026-75829: grav-plugin-api before 1.0.15 Twig SSTI via translate endpoint

> Attackers with write permissions can inject Twig templates via the translate endpoint to execute arbitrary code on the server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/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:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-2jqg-x237-hwx2

## What is CVE-2026-75829?

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

### Official description

grav-plugin-api versions before 1.0.15 fail to validate Twig content in the translate() endpoint, allowing attackers with api.pages.write permission to persist pages with process.twig enabled. Attackers can submit crafted header and content parameters to execute server-side template injection payloads that are evaluated at render time.

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

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


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

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

## Is CVE-2026-75829 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75829 is a high-severity code injection vulnerability in getgrav grav, published on 18 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-75829 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-75829/ (Markdown: https://insights.sbomify.com/CVE-2026-75829/index.md)
```

## Sources

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

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