Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-62230 – Sensitive File Disclosure via .htaccess Case-Sensitivity Bypass – Grav CMS < 2.0.4

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62230 is a high-severity sensitive file disclosure vulnerability affecting Grav CMS versions prior to 2.0.4. The default .htaccess configuration shipped with Grav omits the Apache [NC] (No Case) flag from file-blocking rules, making extension matching case-sensitive. On case-insensitive filesystems, an unauthenticated remote attacker can bypass these protections by requesting sensitive files with uppercase or mixed-case extensions, potentially exposing credentials, API keys, and other secrets stored in Grav configuration files. The CVSS 4.0 score is 8.7 (HIGH).

Technical details

  • Root cause: RewriteRule directives in Grav’s default .htaccess (and the reference webserver-configs/htaccess.txt) block direct HTTP access to sensitive file types — .yaml, .php, .json, .twig, and others — but omit the [NC] (No Case) flag, causing extension matching to be case-sensitive (CWE-178: Improper Handling of Case Sensitivity).
  • Trigger conditions: The bypass is exploitable only on case-insensitive filesystems: Windows/NTFS, macOS/HFS+, or Docker volume mounts originating from either of those operating systems. Linux deployments on case-sensitive filesystems (e.g., ext4) are not affected.
  • Attack vector: An unauthenticated remote attacker sends a crafted HTTP request for a sensitive file using uppercase or mixed-case extensions — for example, /user/accounts/admin.YAML or config.PHP — causing Apache to serve the raw file contents rather than deny access.
  • Impact: Full confidentiality compromise of sensitive configuration data. Grav configuration files commonly store API keys, SMTP passwords, and admin credentials. PHP source files may also be downloaded as plain text rather than executed, exposing application logic.

Affected software

  • Grav CMS (getgrav/grav) — all versions prior to 2.0.4

Severity

  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Grav CMS to version 2.0.4 or later. The 2.0.4 release adds the [NC] flag to the affected RewriteRule directives in .htaccess and webserver-configs/htaccess.txt, enforcing case-insensitive extension matching and closing the bypass.
  • If immediate patching is not possible: Manually add the [NC] flag to the file-extension blocking RewriteRule entries in your .htaccess file. Additionally, restrict public network access to the Grav server at the perimeter level where operationally feasible, and audit exposed configuration directories (/user/accounts/, /user/config/, /user/data/) for signs of unauthorized access.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge