CVE-2026-94361

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

GHSA-x7hw-7xvr-75fq ↗EUVD-2026-114590 ↗

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.
Payable Payment Gateway for WooCommerce < 1.3.1
fixed in 1.3.1
ETK-2026-3155Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 44msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h59m
0
+4h
+6h
+8h
+10h
+12h

description

Payable Payment Gateway for WooCommerce versions before 1.3.1 do not authenticate incoming payment notifications. An unauthenticated remote attacker can alter the paid or failed status of store orders, including orders placed through other payment methods.

mitigation

Update Payable Payment Gateway for WooCommerce to version 1.3.1 or later. Restrict public access to payment-notification endpoints until the update is applied.

fixed in 1.3.1

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.
–
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
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-31 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-3155",
  "cve_id": "CVE-2026-94361",
  "display_id": "CVE-2026-94361",
  "ghsa_id": "GHSA-x7hw-7xvr-75fq",
  "euvd_id": "EUVD-2026-114590",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment-status changes in Payable Payment Gateway",
  "summary": "Payable Payment Gateway for WooCommerce versions before 1.3.1 do not authenticate incoming payment notifications. An unauthenticated remote attacker can alter the paid or failed status of store orders, including orders placed through other payment methods.",
  "mitigation": "Update Payable Payment Gateway for WooCommerce to version 1.3.1 or later. Restrict public access to payment-notification endpoints until the update is applied.",
  "vendor": null,
  "product": "Payable Payment Gateway for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.3.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.3.1"
      ],
      "package_name": "Payable 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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.694972983333333,
  "t0_at": "2026-10-31T06:00:23.604000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-31T06:00:23.604000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-31T06:00:23.604000+00:00",
      "url": "https://github.com/advisories/GHSA-x7hw-7xvr-75fq"
    }
  }
}

published 2026-10-31 07:29Z
last change 2026-10-31 10:50Z

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.