Events Made Easy <= 3.1.3 - Insecure Direct Object Reference to Unauthenticated Person Data Modification
Strategic Overview
- Status
- Patched in 3.1.4
- Affected Plugin
- Events Made Easy
- Affected Version
<= 3.1.3- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-14843
At a glance
CVE-2026-14843 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Events Made Easy WordPress plugin, affecting versions <= 3.1.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.4; sites on affected versions should update now. Disclosed July 2026, reported by Haitam Lazaar.
Vulnerability Overview
The Events Made Easy plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.1.3. This is due to missing ownership verification and nonce check on the change personal information form submission handler, allowing unauthenticated requests to update any person record by IDOR. This makes it possible for unauthenticated attackers to modify personal information of arbitrary persons by supplying a manipulated person_id without authorization.
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 privileges on the target site, and no interaction from a victim user.
CWE-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Events Made Easy <= 3.1.3 takes no account at all. 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 Events Made Easy the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.
Remediation
Update to version 3.1.4, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Events Made Easy 3.1.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Events Made Easy
- 9.8CVE-2022-1905: Events Made Easy <= 2.2.80 SQL Injection
CVE-2022-1905 - 8.8CVE-2023-28660: Events Made Easy <= 2.3.14 SQL Injection
CVE-2023-28660 - 8.8CVE-2021-25030: Events Made Easy <= 2.2.35 Subscriber+ SQL Injection
CVE-2021-25030 - 8.8Events Made Easy < 1.5.50 CSRF to Stored Cross-Site Scripting
- 7.5CVE-2026-75963: Events Made Easy <= 3.2.5 Local File Inclusion
CVE-2026-75963 - 6.1Events Made Easy <= 1.6.20 Stored Cross-Site Scripting
- 5.5CVE-2021-24813: Events Made Easy <= 2.2.23 Admin+ Stored XSS
CVE-2021-24813 - 5.4CVE-2023-0404: Events Made Easy <= 2.3.16 Missing Authorization
CVE-2023-0404
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C