Unauthenticated scheduled-job execution via null token
Published Jul 20, 2026 · Updated Jul 20, 2026
Authentication bypass in Grav Scheduler Webhook Plugin before 1.1.3 allows remote attackers to trigger operator-defined scheduled jobs. Scheduler::processWebhookTrigger() tests the configured token before comparing it, so null short-circuits rejection and accepts a tokenless request. The webhook must be enabled with no token set; one unauthenticated POST runs configured jobs, including shell commands, under the web server account.
Summary
What happened
Authentication bypass in Grav Scheduler Webhook Plugin before 1.1.3 allows remote attackers to trigger operator-defined scheduled jobs. Scheduler::processWebhookTrigger() tests the configured token before comparing it, so null short-circuits rejection and accepts a tokenless request. The webhook must be enabled with no token set; one unauthenticated POST runs configured jobs, including shell commands, under the web server account.
The record
- CVE
- CVE-2026-57852
- Published
- Jul 20, 2026
- Updated
- Jul 20, 2026
- Vendor
- Grav
- Product
- Grav Scheduler Webhook Plugin
- Classifications
- CWE-303, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 20, 2026CVE publishedPublication date reported by the CVE source.
- Jul 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.3
- Affected versionversion=0 <=2.0.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Tokenless scheduler webhook POST proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo