CVE-2026-132773

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

GHSA-4558-rxcv-3h92 ↗EUVD-2026-129343 ↗

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.
Attendize <= 2.8.0
CWE-639 Authorization Bypass Through User-Controlled Key
ETK-2026-4919Zero's internal tracking ID, independent of the CVE number., permanent identifier
8h 23msince last run
43mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+12h18m
0
+2h
+4h
+6h
+8h
+10h

description

Attendize installations through 2.8.0 are affected by an authorization bypass in order cancellation handling. An authenticated organiser may invalidate tickets for attendees of events outside that organiser's account, so access to an organiser account is required.

mitigation

Restrict organiser access to trusted users and promptly review cancellation activity for unexpected cross-event changes. Until a patched release is published, limit exposure by minimizing the number of accounts permitted to manage orders.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
43m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 23:12Z
Δ 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-11-18 23:12Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4919",
  "cve_id": "CVE-2026-132773",
  "display_id": "CVE-2026-132773",
  "ghsa_id": "GHSA-4558-rxcv-3h92",
  "euvd_id": "EUVD-2026-129343",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-event ticket cancellation authorization bypass in Attendize",
  "summary": "Attendize installations through 2.8.0 are affected by an authorization bypass in order cancellation handling. An authenticated organiser may invalidate tickets for attendees of events outside that organiser's account, so access to an organiser account is required.",
  "mitigation": "Restrict organiser access to trusted users and promptly review cancellation activity for unexpected cross-event changes. Until a patched release is published, limit exposure by minimizing the number of accounts permitted to manage orders.",
  "vendor": "Attendize",
  "product": "Attendize",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.8.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Attendize",
      "purl": null
    }
  ],
  "cwes": [
    639
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 43.075953733333336,
  "t0_at": "2026-11-18T23:12:49.534000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T23:12:49.534000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T23:12:49.534000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-132773"
    }
  }
}

published 2026-11-19 10:47Z
last change 2026-11-19 17:22Z

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.