CVE-2026-96200

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

GHSA-8h2p-v5jm-73xp ↗EUVD-2026-90519 ↗

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.
Payments for Hubtel < 1.0.2
fixed in 1.0.2
CWE-862 Missing Authorization
ETK-2026-526, permanent identifier
17d 04h 30msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+70h24m
0
+2h
+4h
+6h
+8h
+10h

description

Payments for Hubtel versions before 1.0.2 do not validate the origin of payment callback notifications. An unauthenticated attacker can cause arbitrary orders to be marked as paid without a corresponding payment. Exposure requires the plugin's payment callback to be reachable.

mitigation

Upgrade Payments for Hubtel to version 1.0.2 or later. Until the update is applied, restrict access to the payment callback to trusted payment-provider sources where possible.

fixed in 1.0.2

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.18%7th percentile
agent run time
33m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 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: 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-01 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-01 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-526",
  "cve_id": "CVE-2026-96200",
  "display_id": "CVE-2026-96200",
  "ghsa_id": "GHSA-8h2p-v5jm-73xp",
  "euvd_id": "EUVD-2026-90519",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment callback spoofing in Payments for Hubtel",
  "summary": "Payments for Hubtel versions before 1.0.2 do not validate the origin of payment callback notifications. An unauthenticated attacker can cause arbitrary orders to be marked as paid without a corresponding payment. Exposure requires the plugin's payment callback to be reachable.",
  "mitigation": "Upgrade Payments for Hubtel to version 1.0.2 or later. Until the update is applied, restrict access to the payment callback to trusted payment-provider sources where possible.",
  "vendor": null,
  "product": "Payments for Hubtel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.0.2"
      ],
      "package_name": "Payments for Hubtel",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 5.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
  "epss_score": 0.0018,
  "epss_percentile": 0.073,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.773791716666665,
  "t0_at": "2026-10-01T06:00:25.812000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T06:00:25.812000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T06:00:25.812000+00:00",
      "url": "https://github.com/advisories/GHSA-8h2p-v5jm-73xp"
    }
  }
}

published 2026-10-04 03:51Z
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.