# CVE-2026-109318: Grav Git Sync 1.0.2 through 3.4.12 Command Injection via Commit Author

> Authenticated content editors can execute OS commands via shell injection in commit author fields when specific author modes are enabled.

- **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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-c89w-55m3-fmf7, GHSA-cp28-795p-j89g

## What is CVE-2026-109318?

CVE-2026-109318 is a high-severity command injection vulnerability in trilbymedia grav-plugin-git-sync, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav Git Sync 1.0.2 through 3.4.12 contains a command injection vulnerability that allows authenticated content editors to execute OS commands by injecting shell substitutions into profile fields. When the gravuser or gravfull author mode is enabled, attackers can set a malicious username, full name, or email that reaches PHP exec() via git commit --author, running commands as the web-server account.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-109318 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109318 is a high-severity command injection vulnerability in trilbymedia grav-plugin-git-sync, published on 12 Oct 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-109318 in the wild and no public exploit code.

Affected product: trilbymedia grav-plugin-git-sync. 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-109318/ (Markdown: https://insights.sbomify.com/CVE-2026-109318/index.md)
```

## Sources

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

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