Quick answers
- Is CVE-2026-65896 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-65896 being exploited in the wild.
- How severe is CVE-2026-65896?
- High severity, with a CVSS score of 7.1, published 23 July 2026.
- Which products and versions are affected?
- Grav API Plugin < 1.0.10.
- Is there a fix for CVE-2026-65896?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-65896 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-65896?
- Check whether you run Grav API Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the `PagesController::move()` method of the Grav API Plugin (getgrav/grav-plugin-api) before version 1.0.10. The application attempts to sanitize the `slug` field using `ltrim($body['slug'], '.')`, which only removes leading periods and fails to neutralize directory traversal sequences like `../` or absolute paths. An authenticated attacker with `api.pages.write` permissions can provide a crafted slug (e.g., `01.home/../../../pwned`) to move a page directory, including its content and media, to any writable location on the server. This bypasses the intended confinement within the `user/pages/` directory and can be used to move files outside the Grav installation root. The issue is addressed in version 1.0.10.
Affected products
- getgrav Grav API Plugin < 1.0.10
Timeline
- 2026-07-09: advisory: GitHub Security Advisory GHSA-qjq4-jp55-4mx2 published
- 2026-07-23: disclosed: CVE-2026-65896 published to NVD