CVE
Attendize authorization bypass in order cancellation
Attendize 2.8.0 and earlier lets an authenticated organiser cancel attendees of other accounts' events. No fixed version is listed.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attendize version 2.8.0 or earlier Attacker holds an authenticated organiser account
Summary
Attendize through 2.8.0 contains an authorization bypass vulnerability in EventOrdersController::postCancelOrder() that allows authenticated organisers to cancel attendees belonging to other accounts' events. Attackers can cancel one of their own orders while supplying foreign attendee IDs, which Attendee::findFromSelection() loads unfiltered, invalidating tickets for any event on the installation.
Who should check
Teams running Attendize 2.8.0 or earlier, where organisers share an installation and could cancel attendees across accounts.
“Attendize through 2.8.0 contains an authorization bypass”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attendize version 2.8.0 or earlier Attacker holds an authenticated organiser accountWorkaround: The facts list no fix and no workaround. Limiting organiser accounts to trusted users reduces exposure to this bug until a fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132773 (Attendize through 2.8.0 Authorization Bypass via postCancelOrder), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132773 (entry last updated 2026-11-18):
Affected:
- Attendize Attendize: through 2.8.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Attendize version 2.8.0 or earlier (source: https://www.vulncheck.com/advisories/attendize-through-2.8.0-authorization-bypass-via-postcancelorder)
- Attacker holds an authenticated organiser account (source: https://www.vulncheck.com/advisories/attendize-through-2.8.0-authorization-bypass-via-postcancelorder)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-132773 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132773 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Attendize/Attendize/issues/1154
- https://github.com/Attendize/Attendize/issues/1156
- https://github.com/Attendize/Attendize/blob/9289acbab1583898fd85aeee66c7b613d8971deb/app/Http/Controllers/EventOrdersController.php#L206-L226
- https://github.com/Attendize/Attendize/blob/9289acbab1583898fd85aeee66c7b613d8971deb/app/Models/Attendee.php#L66-L69
- https://www.vulncheck.com/advisories/attendize-through-2.8.0-authorization-bypass-via-postcancelorder
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132773
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132773"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Attendize Attendize
through 2.8.0
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132773 |
| Record | NVD · CVE-2026-132773 |
| Other links 5 | |
| Report | GitHub · Attendize/Attendize · Issue #1154 |
| Report | GitHub · Attendize/Attendize · Issue #1156 |
| Repository | GitHub · Attendize/Attendize · app/Http/Controllers/EventOrdersController.php · L206-L226 |
| Repository | GitHub · Attendize/Attendize · app/Models/Attendee.php · L66-L69 |
| Link | vulncheck.com · advisories/attendize-through-2.8.0-authorization-bypass-via-postcancelorder |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132773
Is CVE-2026-132773 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authorization check is missing in postCancelOrder, so an organiser account can cancel attendees of events owned by other accounts. The cancelled attendees' tickets are invalidated for any event on the installation.Source: vulncheck.com
Which versions are affected by CVE-2026-132773?
Attendize: through 2.8.0.Source: cve.now feed data
Am I affected, and how do I check?
Attendize version 2.8.0 and earlier is affected, from the first release through 2.8.0. To check the installed version, look at the Attendize version in the installation. The attacker must hold an authenticated organiser account.Source: vulncheck.com
How do I fix CVE-2026-132773?
The facts do not name a fixed version or vendor patch, so no upgrade target is listed. Check the vendor's advisory for a fixed release.Source: vulncheck.com
What if there's no patch?
The facts list no fix and no workaround. Limiting organiser accounts to trusted users reduces exposure to this bug until a fix is available.Source: vulncheck.com