← back to feed
CVE-2026-103381

CVE-2026-103381

validatedZero produced an exploit or a check.

GHSA-qwjc-72ww-h64x ↗EUVD-2026-109620 ↗

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.
Mintpay for WooCommerce <= 2.2.3
ETK-2026-2639Zero's internal tracking ID, independent of the CVE number., permanent identifier
+3h42mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+3h42magent stopped
0
+1h
+2h
+3h
+4h

description

Mintpay for WooCommerce through version 2.2.3 accepts payment callback data without confirming that it originated from a legitimate source. An unauthenticated party may alter order payment or cancellation status and access order information, including customer contact details, if the callback handler is reachable.

mitigation

A fixed version is not identified in the available evidence; apply a vendor update containing a callback-authentication fix when one is available. Until then, restrict access to the callback endpoint to trusted payment-provider sources where feasible and review orders for unexpected status changes.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
<1m
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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-26 06:00Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-qwjc-72ww-h64x
  2. 2026-10-26 06:00Z
  3. 2026-10-26 09:42Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2639",
  "cve_id": "CVE-2026-103381",
  "display_id": "CVE-2026-103381",
  "ghsa_id": "GHSA-qwjc-72ww-h64x",
  "euvd_id": "EUVD-2026-109620",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment callback validation flaw in Mintpay for WooCommerce",
  "summary": "Mintpay for WooCommerce through version 2.2.3 accepts payment callback data without confirming that it originated from a legitimate source. An unauthenticated party may alter order payment or cancellation status and access order information, including customer contact details, if the callback handler is reachable.",
  "mitigation": "A fixed version is not identified in the available evidence; apply a vendor update containing a callback-authentication fix when one is available. Until then, restrict access to the callback endpoint to trusted payment-provider sources where feasible and review orders for unexpected status changes.",
  "vendor": null,
  "product": "Mintpay for WooCommerce",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.2.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Mintpay 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": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.010869066666666666,
  "t0_at": "2026-10-26T06:00:18.388000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-26T09:42:34.045694+00:00",
      "days": 0.15434788997685187,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T06:00:18.388000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-26T06:00:18.388000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T06:00:18.388000+00:00",
      "url": "https://github.com/advisories/GHSA-qwjc-72ww-h64x"
    }
  }
}

published 2026-10-26 09:42Z
last change 2026-10-26 13:07Z

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.