An unauthenticated remote attacker can exploit this by sending a crafted POST request to the /scheduler/webhook endpoint. While the attacker cannot inject arbitrary code, they can force the execution of already-configured scheduled jobs, including those that execute system commands. The impact is limited by the existing server configuration, as the attacker can control the execution timing and select which pre-existing job to trigger, but cannot define the initial task payload. This vulnerability is not present in default Grav installations, as it requires the manual installation of the plugin and specific misconfiguration.

Impact

Successful exploitation allows an unauthenticated attacker to trigger administrative scheduled tasks on the affected server. Depending on the configured jobs, this could lead to unauthorized system command execution, denial of service through resource exhaustion, or the manipulation of application state. The vulnerability affects instances where the scheduler-webhook plugin is enabled without a security token.

Recommendation

• Immediately audit Grav CMS installations to identify instances where the scheduler-webhook plugin is enabled.
• Ensure a strong webhookToken is configured for any enabled webhooks to prevent the short-circuiting logic from bypassing validation.
• Review all configured scheduled jobs for the scheduler-webhook plugin to ensure they do not perform sensitive operations if triggered by unauthorized parties.
• Monitor web server logs for suspicious POST requests targeting the /scheduler/webhook path, particularly those containing the job parameter.