CVE-2026-39518

EventPrime – Events Calendar, Bookings and Tickets <= 4.3.0.0 - Authenticated (Subscriber+) Insecure Direct Object Reference

2026-04-20 00:00
James Pirstin

Strategic Overview

Status
Patched in 4.3.0.1
Affected Plugin
EventPrime – Events Calendar, Bookings and Tickets
Affected Version
<= 4.3.0.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-39518
View all EventPrime – Events Calendar, Bookings and Tickets vulnerabilities

At a glance

CVE-2026-39518 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the EventPrime WordPress plugin, affecting versions <= 4.3.0.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 4.3.0.1; sites on affected versions should update now. Disclosed April 2026, reported by James Pirstin.

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, 4.3.0.0 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform unauthorized actions.

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 <= 4.3.0.0 takes an account at Subscriber level or above. 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 4.3.0.1: builds <= 4.3.0.0 are affected, anything from 4.3.0.1 onward is not.

Remediation

Update to version 4.3.0.1, 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 4.3.0.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-39518https://www.wordfence.com/threat-intel/vulnerabilities/id/77608ee4-1917-4b2c-8acf-5d6087c5ae7ahttps://nvd.nist.gov/vuln/detail/CVE-2026-39518

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C