/

CVE-2026-72546

Severity:

HIGH RISK

(7.1)

IDOR (CWE-639) in Attendize Event Invitation Endpoint

CVE-2026-72546

Deferred

Vulnerability type

Category:

Insecure Direct Object Reference

CWE:

CWE-639

Impact:

Unauthorized cross-account modification of event, attendee, and financial data

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Attendize contains an insecure direct object reference in the postInviteAttendee endpoint, allowing an authenticated event organiser to target events owned by another account. Under deployments where attackers can submit event identifiers to this endpoint, they may inject attendees and orders and alter cross-account event and financial records.

Affected context

The vulnerability occurs in Attendize deployments using the affected invitation endpoint when event lookup relies on a caller-supplied event identifier without verifying that the authenticated organiser owns or is authorized to manage the referenced event. The issue is relevant where authenticated organisers can reach the endpoint and event identifiers are accepted without account-scoped authorization checks.

Exploit preconditions

  • Attack surface: The authenticated postInviteAttendee endpoint
  • Required access: A valid authenticated event organiser account
  • Trigger point: Submission of an attendee or order operation referencing a target event
  • Why exploitation is possible: The target event is loaded by identifier without scoping the lookup to the authenticated organiser's account

Why this happens

The underlying issue is an authorization failure caused by treating a user-controlled object identifier as sufficient authority to access or modify the referenced event. The endpoint retrieves the event without applying an ownership or permission constraint tied to the authenticated organiser. This maps to CWE-639: Authorization Bypass Through User-Controlled Key, commonly described as an insecure direct object reference.

Potential impact

  • Attackers may inject attendees into events owned by other accounts
  • Attackers may create or modify orders across account boundaries
  • Event and financial records could be corrupted or manipulated
  • Affected organisers may experience unauthorized changes to business data
  • Cross-account confidentiality and integrity could be reduced

General mitigation guidance

Mitigation generally focuses on enforcing authorization at the point where every referenced object is retrieved and modified.

Common defensive patterns include:

  • Scope event queries to the authenticated organiser or an explicitly authorized tenant
  • Perform server-side ownership and permission checks for every object identifier
  • Prefer authorization-aware service methods over direct identifier-based lookups
  • Use opaque, non-sequential identifiers as defense in depth rather than as an authorization control
  • Apply least privilege and transaction-level safeguards to attendee and order changes
  • Record and review cross-account authorization failures and sensitive data modifications

How teams detect issues like this

Organizations can identify similar issues through:

  • Static analysis rules that flag object retrieval by request-supplied identifiers without nearby authorization checks
  • Code review checks for tenant, owner, or role constraints on database queries
  • Authorization-focused tests that attempt access to objects belonging to other accounts
  • Policy enforcement requiring centralized, object-level authorization before mutations
  • Audit-log monitoring for unusual cross-account event, attendee, or order changes

Automated code review and security testing tools may help identify missing ownership predicates, but should be supplemented with manual authorization analysis.

Sources

SourceLink
github.comgithub.com/Attendize/Attendize

Frequently asked

questions

It may be exploitable through the application endpoint by an authenticated organiser, provided the endpoint is reachable and accepts references to events outside that organiser's account.

Yes. The described attack requires a valid authenticated event organiser account, but it does not require authorization for the targeted event if the object-level check is missing.

Enforce server-side, object-level authorization and constrain event retrieval and mutation to resources the current organiser is permitted to manage.

Use centralized authorization policies, tenant-scoped queries, negative cross-account tests, and security reviews for every endpoint that accepts object identifiers.

Find out what's already
exploitable in your codebase.