# Grav vulnerable to Path traversal / arbitrary YAML write via user creation leading to Account Takeover / System Corruption

Advisory record · `GHSA-h756-wh59-hhjv`

- **Identifiers:** `GHSA-h756-wh59-hhjv` · `CVE-2025-66295` · `PKSA-87p7-31n6-n4f3`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 2 Dec 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Dec 2025, 01:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `getgrav/grav` (Packagist): affected `<1.8.0-beta.27`; fixed in `1.8.0-beta.27`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Grav versions before 1.8.0-beta.27 (Packagist getgrav/grav) are affected. An administrator with permission to create users can supply a username containing path traversal sequences through the Admin UI, causing Grav to write the account YAML file outside the user/accounts/ directory, which the reporter says can overwrite other YAML files and change another user's email or password. Upgrade to 1.8.0-beta.27 or later. The source gives few details beyond the reporter's test results and does not describe any other mitigation.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0059, the 48th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:02 UTC: First seen by agentprime
- 31 Oct 2026, 14:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h756-wh59-hhjv)

## Sources

- [GitHub Advisory Database: GHSA-h756-wh59-hhjv](https://github.com/advisories/GHSA-h756-wh59-hhjv)
- [OSV: GHSA-h756-wh59-hhjv](https://osv.dev/vulnerability/GHSA-h756-wh59-hhjv)
- <https://github.com/getgrav/grav/security/advisories/GHSA-h756-wh59-hhjv>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-66295>
- <https://github.com/getgrav/grav/commit/3462d94d575064601689b236508c316242e15741>
- <https://github.com/getgrav/grav>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h756-wh59-hhjv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h756-wh59-hhjv/>. Everything for agents: <https://agentprime.io/llms.txt>.
