{
  "id": "CVE-2026-100669",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-100669",
  "published_at": "2026-09-26T13:23:34.082Z",
  "title": "Grav before 2.0.25 Sensitive File Disclosure via Case-Variation Bypass",
  "vendor": "getgrav",
  "product": "grav",
  "cvss": {
    "score": 8.7,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "Grav before 2.0.25 ships web server configuration samples whose access-control deny rules are matched case-sensitively. In webserver-configs/web.config (IIS), every deny rule (user_sensitive_folders, user_accounts, user_data, user_error_redirect, user_pages, system, vendor, ignore_folders) sets ignoreCase=\"false\" on its URL Rewrite \u003cmatch\u003e element, overriding the IIS default of ignoreCase=\"true\"; because these are rewrite matches rather than \u003crequestFiltering\u003e elements, there is no case-insensitive fallback. On IIS running over case-insensitive NTFS, an unauthenticated remote attacker can vary the case of a folder name or file extension (for example GET /user/CONFIG/system.YAML) so that no deny rule matches and the IIS static file handler resolves and returns the underlying file, disclosing sensitive data such as configuration secrets or account password hashes. Whether a bypassed file is actually returned depends on MIME registration: .json is served by default, while .yaml/.yml return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added. The same class of gap exists in the bundled webserver-configs/lighttpd.conf, whose user/(config|env), directory, script-extension, root-file and dotfile rules lack the (?i) modifier, though it is lower risk because lighttpd typically runs on case-sensitive filesystems. Deployments served by Apache (.htaccess), nginx, Caddy, or the PHP built-in server are not affected. The issue is fixed in 2.0.25; because the .htaccess installer heal does not touch web.config or lighttpd.conf, operators must re-copy the corrected sample files after upgrading.",
  "cwe": "CWE-178",
  "cvss_by_source": {
    "cna": 8.7
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "getgrav",
        "product": "grav",
        "ranges": [
          "\u003c 2.0.25"
        ],
        "fixed_in": [
          "2.0.25"
        ]
      }
    ],
    "upgrade": [
      "Upgrade grav to 2.0.25 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/getgrav/grav/security/advisories/GHSA-pg8v-xw58-frq8"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
