On 19 November, VulnCheck published a security advisory (CVE-2026-133117) for WebToffee WooCommerce Product Feeds, a free plugin that builds the product files Google Shopping, Facebook, TikTok, Pinterest and price comparison sites read. In every version before 2.4.4, a stranger could make your store rebuild its product feed over and over, without logging in. Each rebuild eats server power and overwrites the feed file.
I build selling agents for WooCommerce shops, so product data is most of what I look at. The feed is the version of your store that machines read. Google reads it, comparison sites read it, and more AI shopping agents read it every month. If someone can control when that file gets built, they can disturb what those machines see, five days before Black Friday.
The plugin has a "URL cron" option: a link that tells the store to refresh a feed. To keep strangers from using that link, the plugin checks a signature. According to the advisory, the secret behind that signature is one fixed value, the same in every copy of the plugin, and it sits in the public source code. Anyone who reads the code can make a valid signature.
VulnCheck describes the result this way: attackers can send forged requests to an endpoint that needs no login and "repeatedly trigger product-feed generation, causing CPU/database resource exhaustion and overwriting of the generated feed file." VulnCheck rates it 8.8 (high) on CVSS 4.0, and the CVE record also gives a CVSS 3.1 score of 8.2.
Version 2.4.4 came out on WordPress.org on 19 November, and the advisory names it as the fixed version. The 2.4.4 changelog only lists compatibility updates and new UTM and variation options, so do not expect a "security fix" line there. WordPress.org shows more than 2,000 active installations. The Vulners database also lists a public exploit for this CVE on GitHub, posted the same day.
The bug does not expose customer data or payments. It still matters for two reasons.
The first is load. Building a feed means reading every product, price and stock level from the database. A small shop on shared hosting can slow down or go offline if someone triggers that build in a loop. Black Friday is on 27 November, the worst week to learn your hosting cannot take it.
The second is trust in the file. Google Merchant Center, Meta and AI shopping channels treat your feed as the truth about your products. The advisory says the attacker controls the request parameters and that the generated file gets overwritten. It does not say an attacker can write any content they like into the feed. Even so, a feed that rebuilds at random moments, or is half-built when a channel fetches it, can push wrong prices or missing products to places you do not watch. For a skincare shop that can mean the wrong size, the wrong shade or a sold-out serum shown as available.
The premium version of this plugin also builds a feed for OpenAI Agentic Commerce, so ChatGPT shopping can find the catalog. Many shops are heading in that direction. The more channels read one file, the more one weak plugin matters.
At CAIDEL our selling agent works from the merchant's product data, and we see the same thing again and again: when the data is wrong, the agent gives a wrong answer with full confidence. Checking the feed once a week is cheap. Fixing a week of wrong Black Friday listings is not.
Want to see how AI agents read your store today? We built a free snapshot for WooCommerce shops.
Which versions of the WebToffee product feed plugin are affected?
All versions of WebToffee WooCommerce Product Feeds before 2.4.4, according to the VulnCheck advisory for CVE-2026-133117. Version 2.4.4 was released on WordPress.org on 19 November 2026.
Can an attacker steal customer data through this bug?
The advisory does not describe any data theft. It describes forced feed rebuilds without a login, which can overload the server and overwrite the generated feed file.
How do I know if someone tried this on my shop?
Check your server logs for bursts of requests that trigger feed refreshes, look for CPU or database spikes, and check Google Merchant Center for new feed errors since 19 November 2026.