Vulnerability in getgrav/grav (CVE-2026-62673)
Summary
Vulnerability in getgrav/grav (CVE-2026-62673). Risk of unauthorized operations or information disclosure. Exploitable via GET /user/plugins/my-plugin/my-plugin.YAML. Mitigation: upgrade to 2.0.4 or later.
Original description
The description as published by the source.
Grav is a file-based Web platform. Prior to 2.0.4, the Grav .htaccess and webserver-configs/htaccess.txt security rules omit the Apache [NC] flag and therefore compare sensitive directory and file-extension patterns case-sensitively. On a case-insensitive filesystem, an unauthenticated requester can use uppercase directory or extension variants to bypass the rules and retrieve files under user/accounts or user/config, including password hashes and security configuration. This issue is fixed in version 2.0.4.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62673 has been found in getgrav/grav.
Attackers can target a specific entry point like GET /user/plugins/my-plugin/my-plugin.YAML over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade getgrav/grav to 2.0.4 or later.
If unsure, ask your IT team or search "getgrav/grav CVE-2026-62673" on the vendor's site.
CVE-2026-62673 (getgrav/grav) — CWE-178
Attack surface: GET /user/plugins/my-plugin/my-plugin.YAML / plugins
Patched: 2.0.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-178) exists in getgrav/grav. Attackers reach the vulnerable code path via GET /user/plugins/my-plugin/my-plugin.YAML.
Check the vendor advisory for the affected versions of getgrav/grav. Attack surface: GET /user/plugins/my-plugin/my-plugin.YAML / plugins.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.0.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /user/plugins/my-plugin/my-plugin.YAML requests with malformed payloads or SQL meta-characters. Run grep -r 'getgrav/grav' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'getgrav/grav' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
getgrav/gravを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /user/plugins/my-plugin/my-plugin.YAML' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /user/plugins/my-plugin/my-plugin.YAMLへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade getgrav/grav to 2.0.4ステージング環境で 2.0.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /user/plugins/my-plugin/my-plugin.YAML on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web github.com
- web github.com