CVE-2026-108826

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

GHSA-r88v-rcqx-2gj8 ↗EUVD-2026-97330 ↗

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.
Zen Cart 2.2.0; 2.2.1; 2.2.2
ETK-2026-1363Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 15h 59msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h03m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Zen Cart through version 2.2.2 is affected by an SQL injection flaw in the PayPal IPN Handler. A remote attacker who can send input processed by that handler may be able to manipulate database queries via the transaction identifier.

mitigation

Apply patch 557154f4fa025f51553094f47b06aa024220c48f. Until it is applied, restrict exposure of the PayPal IPN Handler to reduce remote attack surface.

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.41%34th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 10:45Z
Δ 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-12 10:45Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 10:45Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1363",
  "cve_id": "CVE-2026-108826",
  "display_id": "CVE-2026-108826",
  "ghsa_id": "GHSA-r88v-rcqx-2gj8",
  "euvd_id": "EUVD-2026-97330",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Zen Cart PayPal IPN Handler",
  "summary": "Zen Cart through version 2.2.2 is affected by an SQL injection flaw in the PayPal IPN Handler. A remote attacker who can send input processed by that handler may be able to manipulate database queries via the transaction identifier.",
  "mitigation": "Apply patch 557154f4fa025f51553094f47b06aa024220c48f. Until it is applied, restrict exposure of the PayPal IPN Handler to reduce remote attack surface.",
  "vendor": null,
  "product": "Zen Cart",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.2.0",
        "2.2.1",
        "2.2.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Zen Cart",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": 0.0041,
  "epss_percentile": 0.3413,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.95620795,
  "t0_at": "2026-10-12T10:45:10.284000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T10:45:10.284000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T10:45:10.284000+00:00",
      "url": "https://github.com/advisories/GHSA-r88v-rcqx-2gj8"
    }
  }
}

published 2026-10-12 13:36Z
last change 2026-10-21 05:31Z

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.