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

Back
New CVE Detected

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

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62673 is a case-sensitivity bypass vulnerability (CWE-178) in Grav CMS affecting all versions prior to 2.0.4. The shipped .htaccess security rules that block direct HTTP access to sensitive files (.yaml, .yml, .php, .json, .twig) are case-sensitive, allowing an unauthenticated remote attacker on a case-insensitive filesystem to bypass them using uppercase file extensions. The issue carries a CVSS score of 8.2 (High) due to the potential for unauthorized disclosure of credentials and configuration data.

Technical details

  • Root cause: RewriteRules in Grav’s .htaccess (and the reference webserver-configs/htaccess.txt) that restrict access to sensitive file extensions omit Apache’s [NC] (No Case) flag, making the extension matching case-sensitive.
  • Trigger conditions: The affected Grav instance must be running on a case-insensitive filesystem — Windows/NTFS, macOS/HFS+, or Linux deployments (e.g., Docker) with volumes mounted from a case-insensitive host.
  • Attack vector: Network-based, unauthenticated, no user interaction required (AV:N/AC:L/PR:N/UI:N). An attacker simply requests a protected file using an uppercase or mixed-case extension (e.g., config.YAML instead of config.yaml) to bypass the blocking rule.
  • Impact: High-confidentiality impact — unauthorized disclosure of sensitive files such as YAML configuration files, credentials, and security settings stored under Grav’s user/ and system/ directories.

Affected software

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

Severity

  • CVSS v4.0 Score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Grav to version 2.0.4 or later, which adds the [NC] flag to the affected RewriteRules.
  • If patching is not immediately possible: Manually add the [NC] flag to the relevant RewriteRules in .htaccess to enforce case-insensitive matching, or deploy Grav only on case-sensitive filesystems (e.g., ext4 on native Linux) until the patch can be applied. Restrict direct web server access to user/ and system/ directories via additional server-level controls as a defense-in-depth measure.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Meta tag generator: GravCMS

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