Event Tickets <= 5.18.1 - Insecure Direct Object Reference to Sensitive Information Exposure

published 2025-01-30 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-51613

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits: 0; none known

The Event Tickets and Registration plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.18.1 via the tc-order-id parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view order details of orders they did not place, which includes ticket prices, user emails and order date.

Patch / fix

fixed in 4 links 1

liquidweb event_tickets 5.18.1.1
liquidweb event_tickets_and_registration 5.18.1.1
theeventscalendar event_tickets 5.18.1.1
tri event_tickets 5.18.1.1

plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3229935%40ev… patch

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 21 mo ago (2025-01-30)

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

stellarwp Event Tickets and Registration

Classification

Weakness

CWE-284 Improper Access Control
CWE-639 Authorization Bypass Through User-Controlled Key

Technology feeds

WordPress rss critical rss

References

Sources

CVE List CVE-2024-13457
NVD CVE-2024-13457

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary