# CVE-2026-65896: Grav API Plugin before 1.0.10 Path Traversal via move

> Authenticated attackers can move page directories to arbitrary locations outside the installation via path traversal in the move endpoint.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 23 Jul 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-hc3p-4h64-j8wr, GHSA-qjq4-jp55-4mx2

## What is CVE-2026-65896?

CVE-2026-65896 is a high-severity path traversal vulnerability in getgrav grav, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav API Plugin (Composer package getgrav/grav-plugin-api) before 1.0.10 fails to properly validate the slug field in the POST /pages/{route}/move endpoint. PagesController::move() sanitizes the slug only with ltrim($body['slug'], '.'), which strips leading periods but does not neutralize '/' or '..' segments. An authenticated API caller with the api.pages.write permission can supply path traversal sequences (e.g., 01.home/../../../pwned) to move an entire page directory (content and media) to an arbitrary writable location outside user/pages/, including outside the Grav installation.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-65896 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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