Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-62230— Grav < 2.0.4 File Access Bypass via Case Variation

Quick assessment

Affected
getgrav grav
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

getgrav Grav是getgrav个人开发者开源的一套可扩展的内容管理系统。 getgrav Grav 2.0.4之前版本存在输入验证错误漏洞,该漏洞源于默认的.htaccess文件缺乏[NC]标志,导致扩展名匹配区分大小写,在不区分大小写的文件系统上,未经身份验证的攻击者可通过请求大写或混合大小写的扩展名绕过限制,读取包含API密钥和凭证的敏感配置文件。

CVSS 7.5 · High EPSS 0.48% · P39

Possible ATT&CK Techniques 1 AI

T1005 · Data from Local System

Affected Version Matrix 2

VendorProduct Version RangeStatus
getgrav grav < 2.0.4 affected
2.0.4 unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-62230

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Grav < 2.0.4 File Access Bypass via Case Variation
Source: CVE Program / CVE List V5
Vulnerability Description
Grav before 2.0.4 ships a default .htaccess (and reference webserver-configs/htaccess.txt) whose rules blocking access to sensitive file types (.yaml, .php, .json, etc.) lack the [NC] flag, making extension matching case-sensitive. On case-insensitive filesystems (Windows/NTFS, macOS/HFS+, or Docker volume mounts), an unauthenticated attacker can request these files with uppercase or mixed-case extensions (e.g., .YAML, .PHP) to bypass the restrictions and read sensitive configuration files that may contain API keys and credentials.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
大小写敏感处理不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
getgrav Grav 输入验证错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
getgrav Grav是getgrav个人开发者开源的一套可扩展的内容管理系统。 getgrav Grav 2.0.4之前版本存在输入验证错误漏洞,该漏洞源于默认的.htaccess文件缺乏[NC]标志,导致扩展名匹配区分大小写,在不区分大小写的文件系统上,未经身份验证的攻击者可通过请求大写或混合大小写的扩展名绕过限制,读取包含API密钥和凭证的敏感配置文件。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
getgrav grav 0 ~ 2.0.4 -

II. Public POCs for CVE-2026-62230

# POC Description Source Link Shenlong Link
AI-Generated POC Premium
Qwen3.6-35B-A3B · 5774 chars
Pro+ exclusive includes:
Vulnerability reproduction recording (real sandbox build + trigger, exclusive)
In-depth vulnerability mechanism
Trigger conditions & impact
Full executable POC code
Exploit chain & mitigation
POC zip download
100+ AI POC generations per month

III. Intelligence Information for CVE-2026-62230

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-62230 (2)

Same Patch Batch · getgrav · 2026-07-17 · 10 CVEs total

CVE-2026-62233 8.8 HIGH grav-plugin-api < 1.0.6 Privilege Escalation via createApiKey
CVE-2026-62234 8.1 HIGH Grav < 2.0.4 SSRF via Unrestricted cURL Protocols
CVE-2026-62231 8.1 HIGH Grav < 1.0.6 API Key Scope Bypass via ApiKeyAuthenticator
CVE-2026-62386 7.5 HIGH Grav < 1.0.0-rc.16 Authentication Bypass via token URL Parameter
CVE-2026-62232 7.4 HIGH Grav < 2.0.4 2FA Bypass via Secret Regeneration
CVE-2026-62387 7.1 HIGH Grav < 1.0.0-rc.16 CORS Misconfiguration via API Plugin
CVE-2026-62237 6.5 MEDIUM Grav < 2.0.4 ReDoS via regex_replace in Sandbox
CVE-2026-62235 6.3 MEDIUM Grav Flex-Objects < 1.4.3 Authorization Bypass via API
CVE-2026-62236 5.4 MEDIUM grav-plugin-login < 3.8.11 CSRF via regenerate2FASecret

IV. Related Vulnerabilities

V. Comments for CVE-2026-62230

No comments yet


Leave a comment