CVE-2026-109516

validatedZero produced an exploit or a check.

GHSA-cw4f-j2mf-3wm9 ↗EUVD-2026-112584 ↗

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).kevAttacks confirmed in the real world.
guruteam Bot for Telegram on WooCommerce <= 1.3.0
CWE-287 Improper Authentication
ETK-2026-2934Zero's internal tracking ID, independent of the CVE number., permanent identifier
+24mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+24magent stopped
0
+5min
+10min
+15min
+20min
+25min

description

Bot for Telegram on WooCommerce versions through 1.3.0 allow unauthenticated attackers to obtain authenticated sessions for WordPress accounts, including administrator accounts. Exploitation requires the plugin's exposed functionality to be reachable and knowledge of a target account username.

mitigation

Disable and remove the plugin, or block public access to its plugin REST API functionality until a corrected release is available. No fixed version is recorded; review for unexpected account sessions and reset affected credentials if compromise is suspected.

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
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 03:39Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-29 03:39Z
    cve_org: trigger signal, started the run
  2. 2026-10-29 04:02Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2934",
  "cve_id": "CVE-2026-109516",
  "display_id": "CVE-2026-109516",
  "ghsa_id": "GHSA-cw4f-j2mf-3wm9",
  "euvd_id": "EUVD-2026-112584",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Bot for Telegram on WooCommerce",
  "summary": "Bot for Telegram on WooCommerce versions through 1.3.0 allow unauthenticated attackers to obtain authenticated sessions for WordPress accounts, including administrator accounts. Exploitation requires the plugin's exposed functionality to be reachable and knowledge of a target account username.",
  "mitigation": "Disable and remove the plugin, or block public access to its plugin REST API functionality until a corrected release is available. No fixed version is recorded; review for unexpected account sessions and reset affected credentials if compromise is suspected.",
  "vendor": "guruteam",
  "product": "Bot for Telegram on WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Bot for Telegram on WooCommerce",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.015077666666666666,
  "t0_at": "2026-10-29T03:39:13.121000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-29T04:02:45.633224+00:00",
      "days": 0.01634852111111111,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T03:39:13.121000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-29T03:39:13.121000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T03:39:13.121000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109516"
    }
  }
}

published 2026-10-29 04:02Z
last change 2026-10-29 07:06Z

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.