← back to feed
CVE-2026-103319

CVE-2026-103319

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

EUVD-2026-109621 ↗

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

description

OPay Payment Gateway for WooCommerce through version 2.5.5 can accept payment notifications without effective origin validation when its signature secret is left at the default empty value. An unauthenticated attacker may falsify notifications and change orders to paid, cancelled, or failed states; the affected installation must retain that empty validation secret.

mitigation

Configure a non-empty secret for validating payment-provider notification signatures and review order status changes for suspicious activity. No fixed version is recorded; monitor the plugin vendor for an update and apply it when available.

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
44m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 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-26 06:00Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-103319

this entry in the feed

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

{
  "etk_id": "ETK-2026-2628",
  "cve_id": "CVE-2026-103319",
  "display_id": "CVE-2026-103319",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-109621",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Payment notification authentication flaw in OPay WooCommerce plugin",
  "summary": "OPay Payment Gateway for WooCommerce through version 2.5.5 can accept payment notifications without effective origin validation when its signature secret is left at the default empty value. An unauthenticated attacker may falsify notifications and change orders to paid, cancelled, or failed states; the affected installation must retain that empty validation secret.",
  "mitigation": "Configure a non-empty secret for validating payment-provider notification signatures and review order status changes for suspicious activity. No fixed version is recorded; monitor the plugin vendor for an update and apply it when available.",
  "vendor": null,
  "product": "OPay Payment Gateway for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "OPay 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": 44.496944066666664,
  "t0_at": "2026-10-26T06:00:18.562000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T06:00:18.562000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T06:00:18.562000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103319"
    }
  }
}

published 2026-10-26 06:41Z
last change 2026-10-26 08:16Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.