Skip to main content
CVE-2026-133117VulnerabilityPublished

WebToffee Product Feed before 2.4.4 for WordPress contains a use of hard-coded cryptographic key vulnerability that

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133117· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 2.4.4 soon.

Data as of 19 Nov 2026, 16:40 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.8
CNA (VulnCheck)CVSS 3.18.2
Patch
Available – fixed in 2.4.4
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More to 2.4.4.

Affected software

ProductAffectedFixed in
webtoffeeWebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & MoreAffected
  • <2.4.4
Fixed in
  • 2.4.4

AI-suggested

Upgrade WebToffee Product Feed to version 2.4.4 or later, where this vulnerability is fixed. Since the vulnerability is due to a hard-coded cryptographic key, patching the plugin to remove or replace the hard-coded key is necessary. No other mitigations are specified or recommended by the vendor advisory data.

Description

WebToffee Product Feed versions prior to 2.4.4 for WordPress contain a vulnerability due to the use of a hard-coded cryptographic key. This flaw allows unauthenticated attackers to bypass the URL-cron signature verification by computing a valid hash with the publicly known constant salt. Exploitation enables attackers to send forged GET requests to an unauthenticated endpoint, triggering repeated product-feed generation that can exhaust CPU and database resources and overwrite the generated feed file.

References

Community reviews

Loading reviews…