CVE-2026-103332

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

GHSA-qxp3-7pvj-q7qx ↗EUVD-2026-110607 ↗

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.
Payex Payment Gateway for Woocommerce <= 1.2.10
ETK-2026-2730Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 24msince 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+0h30m
+2h
+4h
+6h
+8h
+10h
+12h

description

Payex Payment Gateway for WooCommerce through 1.2.10 may accept payment notifications without reliably verifying their origin when its validation secret remains at the default empty value. An unauthenticated remote attacker could cause orders to be recorded as paid under that condition.

mitigation

Set a non-empty, unique validation secret for payment notifications immediately and confirm that notification authentication is enforced. Monitor for and apply a vendor update, as no fixed version is recorded.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-27 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2730",
  "cve_id": "CVE-2026-103332",
  "display_id": "CVE-2026-103332",
  "ghsa_id": "GHSA-qxp3-7pvj-q7qx",
  "euvd_id": "EUVD-2026-110607",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Payment notification authentication flaw in Payex Payment Gateway",
  "summary": "Payex Payment Gateway for WooCommerce through 1.2.10 may accept payment notifications without reliably verifying their origin when its validation secret remains at the default empty value. An unauthenticated remote attacker could cause orders to be recorded as paid under that condition.",
  "mitigation": "Set a non-empty, unique validation secret for payment notifications immediately and confirm that notification authentication is enforced. Monitor for and apply a vendor update, as no fixed version is recorded.",
  "vendor": null,
  "product": "Payex Payment Gateway for Woocommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.2.10"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Payex Payment Gateway for Woocommerce",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.10678385,
  "t0_at": "2026-10-27T06:00:19.925000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T06:00:19.925000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T06:00:19.925000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103332"
    }
  }
}

published 2026-10-27 06:06Z
last change 2026-10-27 07: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.