Attendize Event Data Injection Across Account Boundaries

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. An attacker can modify event data and financial records across account boundaries.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

This insecure direct object reference (IDOR) vulnerability in Attendize allows authenticated event organizers to inject attendees and orders into events belonging to other accounts by exploiting the postInviteAttendee endpoint. The vulnerability stems from insufficient access controls—the endpoint retrieves events by ID alone without validating that the requesting user owns the target event. Attackers can manipulate event data and financial records across account boundaries, making this a critical threat to multi-tenant SaaS platforms. Any organization using Attendize for event management faces exposure to unauthorized data modification, financial fraud, and potential data exfiltration affecting multiple customers simultaneously.

Casky's 283 mapped security skills leverage Claude's extended reasoning to detect the attack patterns underlying TA0004 (Privilege Escalation) and TA0006 (Credential Access) techniques. Practitioners using Casky would identify findings centered on lateral privilege escalation through broken object-level authorization—the platform would flag API endpoints lacking user-scoped filtering, detect object ID manipulation patterns in request payloads, and highlight authorization checks that occur after data retrieval rather than before. Security teams would see anomalous cross-account event modifications, unauthorized order injections, and financial record tampering correlating with authenticated sessions. The extended reasoning capability helps practitioners understand not just that the vulnerability exists, but why the access control failure enables business logic abuse and cross-tenant compromise—critical context for prioritizing remediation and assessing blast radius.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-72546.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-72546

Casky has 283 skills that investigate the attack patterns behind CVE-2026-72546. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn