← Back
CVE-2026-44737

Cross-Site Scripting (XSS) in getgrav/grav (CVE-2026-44737)

Summary

cross-site scripting in getgrav/grav (CVE-2026-44737). Risk of unauthorized operations or information disclosure. Exploitable via `GET /admin/pages/`. Mitigation: upgrade to `1.7.49.5` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44737** has been found in getgrav/grav. Attackers can target a specific entry point like `GET /admin/pages/` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade getgrav/grav to **1.7.49.5** or later. If unsure, ask your IT team or search "getgrav/grav CVE-2026-44737" on the vendor's site.
CVE-2026-44737 (getgrav/grav) — CWE-79 / Attack surface: GET /admin/pages/ Patched: `1.7.49.5` — 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.
❓ What is the problem
**Cross-site scripting (XSS)** (CWE-79) exists in getgrav/grav. Attackers reach the vulnerable code path via `GET /admin/pages/` without authentication.
📍 Affected scope
getgrav/grav — . Attack surface: GET /admin/pages/.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.49.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /admin/pages/` 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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'getgrav/grav' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `getgrav/grav` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect
    grep 'GET /admin/pages/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `GET /admin/pages/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 6
    Apply patch patch
    Upgrade getgrav/grav to 1.7.49.5

    ステージング環境で 1.7.49.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Replay attack against GET /admin/pages/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer getgrav/grav
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.49.5"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →