CVE-2026-32568

waiting for further signalsZero needs more public information before it can validate it.

GHSA-37jp-c43x-pc4v ↗EUVD-2026-93231 ↗

no check availablenot proven exploitable
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.
JMAPlugins WooCommerce Designer Pro >= n/a, <= 1.9.33
ETK-2026-753, permanent identifier
15d 01h 47msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h21m
0
+4h
+6h
+8h
+10h
+12h

description

WooCommerce Designer Pro versions up to and including 1.9.33 are affected. An attacker with a subscriber-level account may be able to execute code on the affected site or server; obtaining that account access is a prerequisite.

mitigation

Restrict or suspend subscriber access where practical, and review subscriber accounts for unauthorized access. Update to a vendor release confirmed to address this issue when available; the evidence does not identify a fixed version.

check
no
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.74%53rd percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 08:33Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-06 08:33Z
    ghsa: trigger signal, started the run
  2. 2026-10-06 08:33Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-753",
  "cve_id": "CVE-2026-32568",
  "display_id": "CVE-2026-32568",
  "ghsa_id": "GHSA-37jp-c43x-pc4v",
  "euvd_id": "EUVD-2026-93231",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Subscriber-authenticated remote code execution in WooCommerce Designer Pro",
  "summary": "WooCommerce Designer Pro versions up to and including 1.9.33 are affected. An attacker with a subscriber-level account may be able to execute code on the affected site or server; obtaining that account access is a prerequisite.",
  "mitigation": "Restrict or suspend subscriber access where practical, and review subscriber accounts for unauthorized access. Update to a vendor release confirmed to address this issue when available; the evidence does not identify a fixed version.",
  "vendor": "JMAPlugins",
  "product": "WooCommerce Designer Pro",
  "affected": [
    {
      "affected_notes": [
        ">= n/a, <= 1.9.33"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "wc-designer-pro",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0074,
  "epss_percentile": 0.5368,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.66495885,
  "t0_at": "2026-10-06T08:33:59.253000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-06T08:33:59.253000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T08:33:59.253000+00:00",
      "url": "https://github.com/advisories/GHSA-37jp-c43x-pc4v"
    }
  }
}

published 2026-10-06 10:31Z
last change 2026-10-21 11:52Z

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.