CVE-2026-11430: Grav CMS Scheduler Webhook Authentication Bypass via Null Short-Circuit

Published Aug 7, 2026
·
Updated

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.

Affected Software

1 affected component
Grav scheduler-webhook plugin (Grav CMS)

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable the scheduler modern webhook feature so the webhook token check/endpoint is not reachable (scheduler.modern.webhook.enabled defaults to false).

    Grav scheduler-webhook plugin / scheduler webhook endpoint scheduler.modern.webhook.enabled = false
  2. Configuration

    If webhook support must be enabled, configure webhookToken; when webhookToken is not configured and scheduler.modern.webhook.enabled is true, token validation is short-circuited and can be bypassed.

    Grav scheduler-webhook plugin webhookToken = configured (non-empty)

Event History

Aug 7, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-11430?

The severity of CVE-2026-11430 is rated high with a score of 7.3.

2

How do I fix CVE-2026-11430?

To fix CVE-2026-11430, ensure that a webhook token is configured in the Grav CMS scheduler-webhook plugin.

3

What type of attack does CVE-2026-11430 allow?

CVE-2026-11430 allows unauthenticated remote attackers to bypass authentication and execute requests using the webhook feature.

4

What actions can be taken by exploiting CVE-2026-11430?

By exploiting CVE-2026-11430, attackers can access the Grav CMS scheduler endpoint without authentication and potentially manipulate scheduled tasks.

5

When was CVE-2026-11430 published?

CVE-2026-11430 was published on August 7, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203