CVE-2026-133117

validatedZero produced an exploit or a check.

EUVD-2026-129920 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+4h17mkevAttacks confirmed in the real world.
WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More < 2.4.4
fixed in 2.4.4
CWE-798 Use of Hard-coded Credentials
ETK-2026-4927Zero's internal tracking ID, independent of the CVE number., permanent identifier
+37mTTV
17mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+0h37magent stoppedpublic poc+4h17m
0
+1h
+2h
+3h
+4h

description

WebToffee WooCommerce Product Feeds for WordPress before 2.4.4 uses a publicly known constant in its URL-cron signature mechanism. An unauthenticated attacker able to reach the endpoint can submit forged requests that repeatedly generate feeds, consuming CPU or database resources and replacing the generated feed file.

mitigation

Upgrade WebToffee WooCommerce Product Feeds to version 2.4.4 or later. Restrict public access to the affected URL-cron endpoint until the update is installed.

fixed in 2.4.4

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 12:29Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+4h17m
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-19 12:29Z
    cve_org: trigger signal, started the run
  2. 2026-11-19 19:49Z

this entry in the feed

GET /api/v1/feed/CVE-2026-133117

{
  "etk_id": "ETK-2026-4927",
  "cve_id": "CVE-2026-133117",
  "display_id": "CVE-2026-133117",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-129920",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded key in WebToffee Product Feed",
  "summary": "WebToffee WooCommerce Product Feeds for WordPress before 2.4.4 uses a publicly known constant in its URL-cron signature mechanism. An unauthenticated attacker able to reach the endpoint can submit forged requests that repeatedly generate feeds, consuming CPU or database resources and replacing the generated feed file.",
  "mitigation": "Upgrade WebToffee WooCommerce Product Feeds to version 2.4.4 or later. Restrict public access to the affected URL-cron endpoint until the update is installed.",
  "vendor": "webtoffee",
  "product": "WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.4.4"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.4.4"
      ],
      "package_name": "WebToffee WooCommerce Product Feeds – Google Shopping, Pinterest, TikTok Ads, & More",
      "purl": null
    }
  ],
  "cwes": [
    798
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 17.219975366666667,
  "t0_at": "2026-11-19T12:29:32.682000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-19T13:06:21.806072+00:00",
      "days": 0.025568565648148148,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T12:29:32.682000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-11-19T16:46:10+00:00",
      "days": 0.17820969907407408,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T12:29:32.682000+00:00",
      "url": "https://github.com/LLCForge/CVE-2026-133117"
    },
    "trigger_signal": {
      "at": "2026-11-19T12:29:32.682000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T12:29:32.682000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-133117"
    }
  }
}

published 2026-11-19 12:49Z
last change 2026-11-19 19:49Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.