CVE-2026-133117: WebToffee Product Feed before 2.4.4 Authorization Bypass via Hard-coded Cron Salt
WebToffee Product Feed before 2.4.4 for WordPress contains a use of hard-coded cryptographic key vulnerability that allows unauthenticated attackers to bypass the URL-cron signature check by computing a valid hash using the publicly known constant salt embedded in the plugin source. Attackers can send forged GET requests with attacker-controlled parameters to the unauthenticated init-hooked endpoint to repeatedly trigger product-feed generation, causing CPU/database resource exhaustion and overwriting of the generated feed file.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to unauthenticated exploitation?
WordPress sites using WebToffee Product Feed versions before 2.4.4 are exposed if the plugin's unauthenticated URL-cron endpoint is reachable. No attacker account or user interaction is required.
What does an attacker need to exploit the issue?
An attacker needs to compute a valid URL-cron signature using the publicly known constant salt embedded in the plugin source, then send forged GET requests with attacker-controlled parameters to the init-hooked endpoint.
What is the practical impact of repeated exploitation?
Repeated forged requests can repeatedly trigger product-feed generation, consuming CPU and database resources. The generated feed file can also be overwritten.
What should be prioritized if the plugin cannot be updated immediately?
The provided information identifies the unauthenticated URL-cron endpoint as the attack path. Prioritize preventing untrusted access to that endpoint until WebToffee Product Feed can be updated to 2.4.4 or later.