EventPrime – Events Calendar, Bookings and Tickets <= 3.5.0 - Insecure Direct Object Reference to (Subscriber+) Arbitrary Booking Update
Strategic Overview
- Status
- Patched in 3.5.0
- Affected Plugin
- EventPrime – Events Calendar, Bookings, Tickets & AI
- Affected Version
<= 3.4.9- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-4665
At a glance
CVE-2024-4665 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the EventPrime WordPress plugin, affecting versions <= 3.4.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.5.0; sites on affected versions should update now. Disclosed October 2024, reported by Felipe Caon.
Vulnerability Overview
The EventPrime – Events Calendar, Bookings and Tickets plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.4.9 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update other user's booking details.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in EventPrime <= 3.4.9 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For EventPrime the fix is 3.5.0: builds <= 3.4.9 are affected, anything from 3.5.0 onward is not.
Remediation
Update to version 3.5.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: EventPrime 3.5.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in EventPrime – Events Calendar, Bookings, Tickets & AI
- 8.1CVE-2026-42687: EventPrime PHP Object Injection
CVE-2026-42687 - 8.1CVE-2026-24378: EventPrime PHP Object Injection
CVE-2026-24378 - 7.5CVE-2026-56053: EventPrime PHP Object Injection
CVE-2026-56053 - 7.2CVE-2026-13441: EventPrime <= 4.3.4.2 Stored Cross-Site Scripting
CVE-2026-13441 - 7.2CVE-2024-12024: EventPrime Stored XSS
CVE-2024-12024 - 6.5CVE-2024-1123: EventPrime Arbitrary Post Overwrite
CVE-2024-1123 - 6.5CVE-2024-1320: EventPrime Stored XSS
CVE-2024-1320 - 6.4CVE-2026-42686: EventPrime Stored XSS
CVE-2026-42686
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C