CVE-2026-11430: Incorrect Implementation of Authentication Algorithm in Trilby Media grav-plugin-scheduler-webhook
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.
AI Analysis
Technical Summary
CVE-2026-11430 describes an authentication bypass in the Grav CMS grav-plugin-scheduler-webhook. When the scheduler-webhook plugin is installed and the webhook feature is enabled (scheduler.modern.webhook.enabled=true) without configuring a webhookToken, a conditional check short-circuits, skipping token validation. This allows unauthenticated remote attackers to trigger already-configured scheduled jobs via POST requests to /scheduler/webhook with a ?job= parameter specifying which job to run. The vulnerability does not allow direct command execution; code execution depends on the operator's job configuration that may shell out. The attacker controls timing and job selection but not the payload or job content. Default Grav or Grav-Admin installations are not affected as the plugin is not installed and the webhook feature is disabled by default.
Potential Impact
An unauthenticated remote attacker can trigger existing scheduled jobs configured by the operator, potentially causing unintended job execution. The attacker cannot create or modify jobs or control job payloads, limiting the impact to timing and selection of pre-existing jobs. Code execution is only possible if the operator has configured a job that executes shell commands. This vulnerability does not affect default Grav installations and requires specific plugin and configuration conditions.
Mitigation Recommendations
No official fix or patch is currently documented. Mitigation involves ensuring that if the scheduler-webhook plugin is installed and the webhook feature is enabled, a webhookToken must be configured to enforce authentication. Alternatively, disable the scheduler-webhook plugin or the webhook feature if not needed. Monitor vendor advisories for updates or official patches. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-11430: Incorrect Implementation of Authentication Algorithm in Trilby Media grav-plugin-scheduler-webhook
Description
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.
CVSS v4.0
Score 6.9medium
Affected software
Trilby Media
grav-plugin-scheduler-webhook
Trilby Media
getgrav/grav
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-11430 describes an authentication bypass in the Grav CMS grav-plugin-scheduler-webhook. When the scheduler-webhook plugin is installed and the webhook feature is enabled (scheduler.modern.webhook.enabled=true) without configuring a webhookToken, a conditional check short-circuits, skipping token validation. This allows unauthenticated remote attackers to trigger already-configured scheduled jobs via POST requests to /scheduler/webhook with a ?job= parameter specifying which job to run. The vulnerability does not allow direct command execution; code execution depends on the operator's job configuration that may shell out. The attacker controls timing and job selection but not the payload or job content. Default Grav or Grav-Admin installations are not affected as the plugin is not installed and the webhook feature is disabled by default.
Potential Impact
An unauthenticated remote attacker can trigger existing scheduled jobs configured by the operator, potentially causing unintended job execution. The attacker cannot create or modify jobs or control job payloads, limiting the impact to timing and selection of pre-existing jobs. Code execution is only possible if the operator has configured a job that executes shell commands. This vulnerability does not affect default Grav installations and requires specific plugin and configuration conditions.
Mitigation Recommendations
No official fix or patch is currently documented. Mitigation involves ensuring that if the scheduler-webhook plugin is installed and the webhook feature is enabled, a webhookToken must be configured to enforce authentication. Alternatively, disable the scheduler-webhook plugin or the webhook feature if not needed. Monitor vendor advisories for updates or official patches. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-05T21:01:53.800Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a76350bbf8831d5390b01b9
Added to database: 08/07/2026, 19:42:03 UTC
Last enriched: 08/15/2026, 14:29:34 UTC
Last updated: 09/21/2026, 22:01:32 UTC
Views: 84
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.