CVE-2026-72547

Attendize Attendize - Insecure Direct Object Reference

Published Aug 11, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
Description
An insecure direct object reference vulnerability in Attendize through commit 9289acb allows any authenticated event organiser to bulk import attendees into events belonging to other accounts via the postImportAttendee endpoint. The endpoint loads the target event by ID without verifying ownership against the requesting organiser account. An attacker can inject bulk attendee data into any event in the system regardless of account boundaries.

Analysis

AI-generated

Technical impact

This vulnerability is an insecure direct object reference (CWE-639) that allows any authenticated event organiser to use the postImportAttendee endpoint to load attendee data into events that belong to other accounts. The endpoint identifies the target event solely by its numeric ID and does not verify that the requesting organiser actually owns that event. As a result, an attacker can inject bulk attendee records into any event in the system, violating the principle of ownership and exposing private participant information.

Affected Systems

The affected product is Attendize, the open‑source event management platform. The flaw exists in all releases that contain commit 9289acb or later, with no known version boundaries provided by the CNA.

Risk and Exploitability

The CVSS score of 7.1 signals a high severity risk, although the EPSS score is not available so the precise exploitation probability cannot be quantified. The flaw is not listed in the CISA KEV catalog. The likely attack path requires an authenticated organiser's account; the attacker simply submits an import request with the target event ID of another account’s event. No additional system privileges are needed beyond normal organiser authentication, making this a high‑impact vulnerability for multi‑tenant deployments.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Verify that the event ID supplied to the bulk import endpoint belongs to the authenticated organiser before processing the request.
  • Disable or restrict the bulk import feature for events that are not owned by the current organiser to prevent cross‑account data injection.
  • Apply any official patch or update from Attendize that implements ownership checks once it becomes available; until then, consider blocking the postImportAttendee endpoint or replacing it with a controlled, verified import workflow.

Generated by OpenCVE AI on August 11, 2026 at 17:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Attendize
Attendize attendize
Vendors & Products Attendize
Attendize attendize
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description An insecure direct object reference vulnerability in Attendize through commit 9289acb allows any authenticated event organiser to bulk import attendees into events belonging to other accounts via the postImportAttendee endpoint. The endpoint loads the target event by ID without verifying ownership against the requesting organiser account. An attacker can inject bulk attendee data into any event in the system regardless of account boundaries.
Title Attendize Attendize - Insecure Direct Object Reference
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
TuranSec
Published
Updated
Aug 11, 2026, 3:10 PM
Reserved
Aug 10, 2026, 10:32 AM
Status
Deferred
Published
Aug 11, 2026, 12:17 PM
Modified
Oct 24, 2026, 3:10 PM