Vulnerability in Grav CMS (CVE-2026-11430)
Summary
Vulnerability in Grav CMS (CVE-2026-11430). Risk of unauthorized operations or information disclosure. Exploitable via POST /scheduler/webhook.
Original description
The description as published by the source.
Grav CMS's scheduler-webhook plugin contains an authentication bypass in the webhook token check. When the webhook feature is enabled but no webhookToken is configured, a compound conditional short-circuits and skips token validation, so an unauthenticated remote attacker who can reach POST /scheduler/webhook can trigger the operator's already-configured scheduled jobs by sending a single request. The primitive is triggering-existing-jobs, not attacker-chosen command execution: the attacker controls when the jobs run and which one runs (via ?job=), but does not control what the jobs do. Code execution follows only when the operator has configured a job that shells out, and even then the attacker controls timing rather than payload. Not a default-install issue: reaching the endpoint requires the separate scheduler-webhook GPM plugin to be installed, scheduler.modern.webhook.enabled to be true (default false), and no webhookToken to be configured; a stock Grav or Grav-Admin install exposes nothing here.
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-11430 has been found in Grav CMS.
Attackers can target a specific entry point like POST /scheduler/webhook over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Grav CMS CVE-2026-11430" on the vendor's site.
CVE-2026-11430 (Grav CMS) — CWE-303 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /scheduler/webhook
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-303) exists in Grav CMS. Attackers reach the vulnerable code path via POST /scheduler/webhook without authentication.
Check the vendor advisory for the affected versions of Grav CMS. Attack surface: POST /scheduler/webhook.
Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /scheduler/webhook requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Grav CMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /scheduler/webhook' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /scheduler/webhookへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /scheduler/webhook on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。