Skip to content
Fencer Intel
high 8.8

CVE-2026-133117 json

WebToffee Product Feed before 2.4.4 Authorization Bypass via Hard-coded Cron Salt

published 18h ago modified 13h ago also EUVD-2026-129920

cvss
8.8
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More 2.4.4

Is CVE-2026-133117 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
14h ago

CVSS scores

assigned by version score vector
CNA 4.0 8.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
CNA 3.1 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Affected products

  • webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.