CVE-2026-72695

Grav: Path Traversal in MediaUploadTrait::deleteFile() Allows Arbitrary File Deletion

An authenticated user with media management permissions can:

• Delete configuration files (user/config/system.yaml, user/config/security.yaml)
• Delete other pages' content files
• Delete authentication-related files (user account YAML files)
• Cause denial of service by removing critical application files
• Potentially escalate privileges by removing security configuration

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-72695 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.0.16); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Apply Utils::checkFilename() to the full $filename parameter before decomposing it, or reject any filename containing directory separators or .. sequences:

public function deleteFile(string $filename, ?array $settings = null): void
{
    $settings = $this->getUploadSettings($settings);
    $filesystem = Filesystem::getInstance(false);

    // Validate the FULL filename, not just the basename
    if (!Utils::checkFilename($filename)) {
        throw new RuntimeException(/* ... */);
    }

    // ... rest unchanged
}

The same fix should be applied to renameFile() for both $from and $to parameters.

1. What is CVE-2026-72695? CVE-2026-72695 is a high-severity path traversal vulnerability in getgrav/grav (composer), affecting versions <= 2.0.15. It is fixed in 2.0.16. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-72695? CVE-2026-72695 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of getgrav/grav are affected by CVE-2026-72695? getgrav/grav (composer) versions <= 2.0.15 is affected.
4. Is there a fix for CVE-2026-72695? Yes. CVE-2026-72695 is fixed in 2.0.16. Upgrade to this version or later.
5. Is CVE-2026-72695 exploitable, and should I be worried? Whether CVE-2026-72695 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-72695 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-72695? Upgrade getgrav/grav to 2.0.16 or later.

Other vulnerabilities in getgrav/grav