CVE-2026-93836

validatedZero produced an exploit or a check.

GHSA-m435-6crg-xq92 ↗EUVD-2026-84310 ↗

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.+14d
wpclever wpc_product_bundles_for_woocommerce <= 8.6.6
ETK-2026-1276Zero's internal tracking ID, independent of the CVE number., permanent identifier
+20dTTV
55mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
cve.org publication−14dtrigger signal +0dkev+1.0dcheck available+6.1dagent stopped
−10d
−5d
0
+5d

description

WPC Product Bundles for WooCommerce versions through 8.6.6 can store script-bearing content submitted through a bundle quantity field. An unauthenticated attacker may cause browser-side code to run for users who later view the affected stored content.

mitigation

Deactivate WPC Product Bundles for WooCommerce until the maintainer provides a corrected release; no fixed version is recorded. If it must remain installed, restrict public access to workflows that accept bundle quantity submissions and review affected order metadata for injected content.

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.
0.24%14th percentile
agent run time
55m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-22 07:41Z
Δ 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.
+14d

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-09-22 07:41Z
  2. 2026-10-06
    vulncheck_kev: trigger signal, started the run
  3. 2026-10-06 00:00Z
  4. 2026-10-12 09:02Z
    Attackers Exploit CVSS 10.0 Bricksforge WordPress Flaw Enabling Unauthenticated RCE

this entry in the feed

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

{
  "etk_id": "ETK-2026-1276",
  "cve_id": "CVE-2026-93836",
  "display_id": "CVE-2026-93836",
  "ghsa_id": "GHSA-m435-6crg-xq92",
  "euvd_id": "EUVD-2026-84310",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in WPC Product Bundles for WooCommerce",
  "summary": "WPC Product Bundles for WooCommerce versions through 8.6.6 can store script-bearing content submitted through a bundle quantity field. An unauthenticated attacker may cause browser-side code to run for users who later view the affected stored content.",
  "mitigation": "Deactivate WPC Product Bundles for WooCommerce until the maintainer provides a corrected release; no fixed version is recorded. If it must remain installed, restrict public access to workflows that accept bundle quantity submissions and review affected order metadata for injected content.",
  "vendor": "wpclever",
  "product": "wpc_product_bundles_for_woocommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 8.6.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WPC Product Bundles for WooCommerce",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": 0.0024,
  "epss_percentile": 0.1452,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 54.71423763333333,
  "t0_at": "2026-09-22T07:41:16.170000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-12T01:45:15.434606+00:00",
      "days": 19.752769266273148,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T07:41:16.170000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-10-06T00:00:00+00:00",
      "days": 14,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T07:41:16.170000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-93836"
    },
    "trigger_signal": {
      "at": "2026-10-06T00:00:00+00:00",
      "days": 13.679673958333334,
      "is_lower_bound": false,
      "measured_at": "2026-09-22T07:41:16.170000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-93836"
    }
  }
}

published 2026-10-12 00:50Z
last change 2026-10-21 05:00Z

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.