PatchSiren cyber security CVE debrief
CVE-2026-72546 Attendize CVE debrief
An insecure direct object reference vulnerability in Attendize through commit 9289acb allows any authenticated event organiser to inject attendees and orders into events belonging to other accounts via the postInviteAttendee endpoint. The endpoint loads the target event by ID without scoping the query to the authenticated organiser account. This vulnerability enables attackers to modify event data and financial records across account boundaries, potentially impacting event management and financial operations. Organisations should verify their instance's security and monitor for suspicious activity. The CVE record was published on 2026-08-11T12:17:40.110Z and has not been modified since then. To address this vulnerability, organisations should focus on securing their event management systems and ensuring that access controls are properly implemented.
- Vendor
- Attendize
- Product
- Unknown
- CVSS
- HIGH 7.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-11
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-08-11
- Advisory updated
- 2026-09-03
Who should care
Organisations using Attendize for event management, particularly those with multiple accounts or high-value events, should verify their instance's security and monitor for suspicious activity. This includes event organisers, financial teams, and security personnel who may be impacted by the potential modification of event data and financial records.
Technical summary
The postInviteAttendee endpoint in Attendize through commit 9289acb is vulnerable to insecure direct object reference. This allows any authenticated event organiser to inject attendees and orders into events belonging to other accounts. The endpoint fails to scope the query to the authenticated organiser account, enabling attackers to modify event data and financial records across account boundaries. This vulnerability can be addressed by securing the endpoint and ensuring proper access controls are in place.
Defensive priority
Authenticated attackers may inject attendees and orders into events across account boundaries, allowing modification of event data and financial records.
Recommended defensive actions
- Verify event organiser account permissions and access controls
- Restrict postInviteAttendee endpoint access to authorised accounts
- Monitor event data and financial records for suspicious activity
- Implement scoping of queries to authenticated organiser accounts
- Review and update Attendize to commit 9289acb or later
- Conduct a thorough review of event management systems for potential vulnerabilities
- Implement additional monitoring and logging to detect suspicious activity
Evidence notes
The CVE record indicates an insecure direct object reference vulnerability in Attendize through commit 9289acb. The postInviteAttendee endpoint allows authenticated event organisers to inject attendees and orders into events belonging to other accounts. The endpoint loads the target event by ID without scoping the query to the authenticated organiser account.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-72546 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-72546
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-72546 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-72546
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/Attendize/Attendize
309f9ea4-e3e9-4c6c-b79d-e8eb01244f2c
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.