CVE-2026-104745

validatedZero produced an exploit or a check.

GHSA-hrmj-f3f9-pq8r ↗EUVD-2026-102615 ↗

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).+2h44mkevAttacks confirmed in the real world.
wpcodefactory Customer Email Verification for WooCommerce <= 3.3.0
CWE-269 Improper Privilege Management
ETK-2026-1772Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.3dTTV
40mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+2h44mcheck available+31h43magent stopped
0
+6h
+12h
+18h
+24h

description

Customer Email Verification for WooCommerce through 3.3.0 can allow an unauthenticated party to authenticate as an unverified WordPress user, potentially including a privileged user. Exposure depends on the plugin using the hashids encoding option and the target account still being unverified.

mitigation

Change the plugin's Encoding method away from hashids immediately, or deactivate the plugin if that is not possible. Review and verify or disable unverified privileged accounts, and apply a vendor update when a corrected release is published.

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.52%42nd percentile
agent run time
40m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 03:38Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2h44m
Δ 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-10-16 03:38Z
    cve_org: trigger signal, started the run
  2. 2026-10-17 10:31Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1772",
  "cve_id": "CVE-2026-104745",
  "display_id": "CVE-2026-104745",
  "ghsa_id": "GHSA-hrmj-f3f9-pq8r",
  "euvd_id": "EUVD-2026-102615",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Privilege escalation in Customer Email Verification for WooCommerce",
  "summary": "Customer Email Verification for WooCommerce through 3.3.0 can allow an unauthenticated party to authenticate as an unverified WordPress user, potentially including a privileged user. Exposure depends on the plugin using the hashids encoding option and the target account still being unverified.",
  "mitigation": "Change the plugin's Encoding method away from hashids immediately, or deactivate the plugin if that is not possible. Review and verify or disable unverified privileged accounts, and apply a vendor update when a corrected release is published.",
  "vendor": "wpcodefactory",
  "product": "Customer Email Verification for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Customer Email Verification for WooCommerce",
      "purl": null
    }
  ],
  "cwes": [
    269
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0052,
  "epss_percentile": 0.4291,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 39.544780616666664,
  "t0_at": "2026-10-16T03:38:41.491000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-17T11:21:40.451804+00:00",
      "days": 1.3215157500462964,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T03:38:41.491000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-16T06:22:45+00:00",
      "days": 0.11392950231481482,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T03:38:41.491000+00:00",
      "url": "https://github.com/rxsklife/CVE-2026-104745"
    },
    "trigger_signal": {
      "at": "2026-10-16T03:38:41.491000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T03:38:41.491000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104745"
    }
  }
}

published 2026-10-16 11:51Z
last change 2026-10-21 09:20Z

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.