CVE-2026-65896: External Control of File Name or Path in getgrav grav
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.
AI Analysis
Technical Summary
The Grav API Plugin (getgrav/grav-plugin-api) before version 1.0.10 improperly sanitizes the slug parameter in the POST /pages/{route}/move endpoint by only removing leading periods but failing to neutralize path traversal sequences such as '/' or '..'. This allows an authenticated API user with the api.pages.write permission to move entire page directories, including content and media, to arbitrary writable locations outside the user/pages/ directory and potentially outside the Grav installation root. This vulnerability is tracked as CVE-2026-65896 and has a CVSS 4.0 base score of 7.1, indicating high severity.
Potential Impact
An attacker with authenticated API access and the api.pages.write permission can perform directory traversal via crafted slug values, enabling them to move page directories to arbitrary writable locations outside the designated content directory. This could result in unauthorized file system modifications, potentially affecting the integrity and availability of the Grav installation's content and media files.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict api.pages.write permissions to trusted users only and monitor for suspicious API activity involving the move endpoint. Avoid exposing the API to untrusted networks.
CVE-2026-65896: External Control of File Name or Path in getgrav grav
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.
CVSS v4.0
Score 7.1high
Affected software
pkg:composer/getgrav/grav-plugin-apiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Grav API Plugin (getgrav/grav-plugin-api) before version 1.0.10 improperly sanitizes the slug parameter in the POST /pages/{route}/move endpoint by only removing leading periods but failing to neutralize path traversal sequences such as '/' or '..'. This allows an authenticated API user with the api.pages.write permission to move entire page directories, including content and media, to arbitrary writable locations outside the user/pages/ directory and potentially outside the Grav installation root. This vulnerability is tracked as CVE-2026-65896 and has a CVSS 4.0 base score of 7.1, indicating high severity.
Potential Impact
An attacker with authenticated API access and the api.pages.write permission can perform directory traversal via crafted slug values, enabling them to move page directories to arbitrary writable locations outside the designated content directory. This could result in unauthorized file system modifications, potentially affecting the integrity and availability of the Grav installation's content and media files.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict api.pages.write permissions to trusted users only and monitor for suspicious API activity involving the move endpoint. Avoid exposing the API to untrusted networks.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-23T11:03:13.092Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6207989c2644c7f80b69fe
Added to database: 07/23/2026, 12:22:48 UTC
Last enriched: 07/30/2026, 22:47:11 UTC
Last updated: 09/04/2026, 22:52:14 UTC
Views: 95
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.