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.
References
Configurations
No configuration.
History
No history.
Information
Published : 2026-08-07 19:17
Updated : 2026-08-31 20:19
NVD link : CVE-2026-11430
Mitre link : CVE-2026-11430
CVE.ORG link : CVE-2026-11430
JSON object : View
Products Affected
No product.
CWE
CWE-303
Incorrect Implementation of Authentication Algorithm
