CVE-2026-92437

validatedZero produced an exploit or a check.

GHSA-g66g-hh39-fx5j ↗EUVD-2026-91945 ↗

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.
Mailchimp for WooCommerce < 6.3
fixed in 6.3
CWE-862 Missing Authorization
ETK-2026-593, permanent identifier
+1.7dTTV
38mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+40h11magent stopped
0
+12h
+24h
+36h

description

Mailchimp for WooCommerce versions earlier than 6.3 are affected. An unauthenticated remote attacker may alter or delete abandoned-cart records associated with other customers when the plugin accepts supplied cart identifiers.

mitigation

Upgrade Mailchimp for WooCommerce to version 6.3 or later.

fixed in 6.3

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.22%11th percentile
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 06:00Z
Δ 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

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-03 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-03 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-593",
  "cve_id": "CVE-2026-92437",
  "display_id": "CVE-2026-92437",
  "ghsa_id": "GHSA-g66g-hh39-fx5j",
  "euvd_id": "EUVD-2026-91945",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated abandoned-cart access control flaw in Mailchimp for WooCommerce",
  "summary": "Mailchimp for WooCommerce versions earlier than 6.3 are affected. An unauthenticated remote attacker may alter or delete abandoned-cart records associated with other customers when the plugin accepts supplied cart identifiers.",
  "mitigation": "Upgrade Mailchimp for WooCommerce to version 6.3 or later.",
  "vendor": null,
  "product": "Mailchimp for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 6.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.3"
      ],
      "package_name": "Mailchimp for WooCommerce",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 5.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
  "epss_score": 0.0022,
  "epss_percentile": 0.1185,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 38.35489585,
  "t0_at": "2026-10-03T06:00:27.350000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-04T22:11:33.281398+00:00",
      "days": 1.6743742059953703,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T06:00:27.350000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-03T06:00:27.350000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T06:00:27.350000+00:00",
      "url": "https://github.com/advisories/GHSA-g66g-hh39-fx5j"
    }
  }
}

published 2026-10-04 21:33Z
last change 2026-10-21 04:45Z

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.