Skip to content
Threat Feed
high advisory

Grav .htaccess Case-Insensitive Extension Bypass

A misconfigured .htaccess file in Grav allows unauthenticated remote attackers to bypass access restrictions and download sensitive configuration and source files by utilizing uppercase file extensions on case-insensitive filesystems.

CVE search metadata

CVE search record: CVE-2026-62673. KEV: no. Product: Grav (2.0.1). Brief: Grav .htaccess Case-Insensitive Extension Bypass. Brief link: https://feed.craftedsignal.io/briefs/2026-08-grav-htaccess-bypass/

Grav CMS (v2.0.1 and earlier) utilizes an .htaccess file to restrict access to sensitive file types stored within the user/ and system/vendor/ directories. These directives are intended to return a 403 Forbidden status for requests targeting files with extensions such as .yaml, .json, and .php. However, the current configuration rules lack the [NC] (No Case) Apache directive flag.

On case-insensitive filesystems, such as NTFS (Windows) or HFS+ (macOS), the operating system resolves uppercase extensions to the same file path as their lowercase counterparts, but the web server fails to match the blocking rule. Consequently, an attacker can access sensitive data by requesting files with uppercase extensions (e.g., .YAML instead of .yaml). This can lead to the exposure of API keys, administrative credentials, and application source code, depending on the server configuration. The vulnerability is mitigated on native Linux distributions utilizing case-sensitive filesystems like ext4.

Impact

The vulnerability results in unauthorized information disclosure of critical configuration and source files. Attackers can exfiltrate sensitive plugin data (including API keys), system configuration files (system.yaml), and potentially source code if the server is configured to serve .PHP files as static content rather than executing them. This impacts any Grav instance deployed on Windows, macOS, or Docker environments with volumes mounted from these systems.

Recommendation

  • Immediately update to Grav version 2.0.4 or later where the missing [NC] flags have been applied to the rewrite rules.
  • If immediate patching is not possible, manually edit the root .htaccess file to append the [NC] flag to the relevant RewriteRule definitions on lines 68, 70, and 72.
  • Review Apache web server logs for HTTP 200 responses to requests targeting sensitive file types with non-standard capitalization, specifically focusing on user/ and system/vendor/ URI paths.
  • Audit infrastructure deployments to ensure that web-facing sensitive directories are not hosted on case-insensitive volumes.

Immediate actions

Deploy updated .htaccess rules or update to Grav 2.0.4

IT Operations 48h

Threat Hunt

Search web logs for 200 responses to sensitive extensions in /user/ or /system/ directories

T1190 high high confidence hunt now

Data: webserver_access_logs

Mitigations

Patch web server configuration

immediate IT Operations

CVE-2026-62673

Detection coverage 1

Detect CVE-2026-62673 Exploitation - Unauthorized Access to Sensitive Grav Files

high

Detects potential exploitation of CVE-2026-62673 by identifying successful HTTP 200 responses for sensitive file types in restricted directories, specifically where the request URI contains uppercase extensions.

sigma tactics: initial_access techniques: T1190 sources: webserver

Detection queries are available on the platform. Get full rules →