CVE-2026-94275

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

GHSA-f82x-57h2-9789 ↗EUVD-2026-94754 ↗

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.
Track Orders for WooCommerce < 1.2.7
fixed in 1.2.7
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-1340Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 16h 38msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+102h11m
0
+2h
+4h
+6h
+8h
+10h

description

Track Orders for WooCommerce versions before 1.2.7 may expose customer billing details and order history because order ownership is not verified before returning data. An unauthenticated attacker may retrieve this information if they know or can supply a customer's email address.

mitigation

Update Track Orders for WooCommerce to version 1.2.7 or later. Restrict public access to order-tracking functionality until the update is applied.

fixed in 1.2.7

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.21%10th percentile
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1340",
  "cve_id": "CVE-2026-94275",
  "display_id": "CVE-2026-94275",
  "ghsa_id": "GHSA-f82x-57h2-9789",
  "euvd_id": "EUVD-2026-94754",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing order authorization in Track Orders for WooCommerce",
  "summary": "Track Orders for WooCommerce versions before 1.2.7 may expose customer billing details and order history because order ownership is not verified before returning data. An unauthenticated attacker may retrieve this information if they know or can supply a customer's email address.",
  "mitigation": "Update Track Orders for WooCommerce to version 1.2.7 or later. Restrict public access to order-tracking functionality until the update is applied.",
  "vendor": null,
  "product": "Track Orders for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.2.7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.2.7"
      ],
      "package_name": "Track Orders for WooCommerce",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 5.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1005,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.578120866666666,
  "t0_at": "2026-10-08T06:00:09.401000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T06:00:09.401000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T06:00:09.401000+00:00",
      "url": "https://github.com/advisories/GHSA-f82x-57h2-9789"
    }
  }
}

published 2026-10-12 09:45Z
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.