WebToffee WooCommerce Product Feeds authorization bypass via hard-coded cron salt
Affects WebToffee Product Feed before 2.4.4 for WordPress, where the URL-cron signature check uses a hard-coded key. Fixed in 2.4.4.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.4.4
- Who is exposed
- Not reported
Summary
The WebToffee Product Feed plugin for WordPress has an authorization bypass. A remote attacker, without logging in, can send forged requests that trigger product-feed generation, which can exhaust CPU and database resources and overwrite the generated feed file.
Written by a model
Original description
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.
Who should check
Sites running the WebToffee WooCommerce Product Feeds (Google Shopping, Pinterest, TikTok Ads) plugin before 2.4.4 on WordPress with WooCommerce.
“WebToffee Product Feed before 2.4.4 for WordPress”
What to do
Upgrade to a fixed version: 2.4.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133117 (WebToffee Product Feed before 2.4.4 Authorization Bypass via Hard-coded Cron Salt), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133117 (entry last updated 2026-11-19):
Affected:
- webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More: fixed in 2.4.4
Fixed versions: 2.4.4.
Conditions (all must be true for the bug to be hit):
- WebToffee Product Feed version before 2.4.4 for WordPress (source: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt)
- The URL-cron signature check endpoint is reachable and unauthenticated (init-hooked) (source: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133117 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133117 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://wordpress.org/plugins/webtoffee-product-feed/#developers
- https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133117
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133117"}.Affected versions
- webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & Morefixed in 2.4.4
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133117 |
| Record | NVD · CVE-2026-133117 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-133117 · Repository |
| Other links 2 | |
| Patch | wordpress.org · plugins/webtoffee-product-feed#developers |
| Link | vulncheck.com · advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt |
Questions about CVE-2026-133117
Is CVE-2026-133117 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The plugin's URL-cron signature check uses a hard-coded cryptographic key, so an unauthenticated request can bypass the check. That lets an attacker repeatedly trigger product-feed generation, exhaust CPU and database resources, and overwrite the generated feed file.
Source: vulncheck.com
Which versions are affected by CVE-2026-133117?
WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More: before 2.4.4.
Source: cve.now feed data
Am I affected, and how do I check?
WebToffee Product Feed versions before 2.4.4 for WordPress are affected. The problem is in the URL-cron signature check endpoint, which is reachable without authentication and hooked into init. The plugin version can be checked on the WordPress Plugins screen or in the plugin's main file header.
Source: vulncheck.com
How do I fix CVE-2026-133117?
Upgrade WebToffee Product Feed to version 2.4.4, which is the listed fixed version. The advisory names no separate patch identifiers.
Source: vulncheck.com
Related
- CVE-2026-104368Export and Import Users and Customers <= 2.7.5 - Authenticated (Subscriber+) Privilege Escalation via CSV Escape-Character Mismatch in…
- CVE-2026-32441WordPress Comments Import & Export plugin <= 2.4.9 - Broken Access Control vulnerability
- CVE-2026-93746WebToffee WooCommerce PDF Invoices, Packing Slips, Delivery Notes & Shipping Labels <= 5.0.2 - Insecure Direct Object Reference to Unauthenticated Unauthorized Order Document Access via 'email' Parameter
- CVE-2026-97197WordPress WordPress Backup & Migration plugin <= 1.6.0 - Broken Access Control vulnerability
- CVE-2026-49056WordPress WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels plugin <= 4.9.4 - Sensitive Data Exposure vulnerability
- CVE-2026-45438WordPress Smart Coupons for WooCommerce plugin < 2.3.0 - Broken Access Control vulnerability
No corrections so far. Something wrong on this page? Report an error.