CVE-2026-14280: Events Manager <= 7.3.7.4 - Authenticated (Administrator+) Local File Inclusion via 'dbem_data[updates]' Array Keys
The Events Manager – Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 7.3.7.4 via the emoptionssave function. This makes it possible for authenticated attackers, with administrator-level access and above, to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The stored traversal key is subsequently executed via an includeonce() call that fires on every admininit invocation — including unauthenticated admin-ajax.php requests — meaning once the malicious key is stored by an administrator, the inclusion is triggered without any further authentication or capability check.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
WordPress Events Manager pluginto a version that resolves this vulnerability.Fixed in 7.3.7.4 - Compensating control
Restrict access to WordPress admin-ajax.php so unauthenticated requests cannot reach admin_init (the include_once() executes on every admin_init invocation, including admin-ajax.php requests).
Event History
Frequently Asked Questions
Who can exploit this issue initially?
An authenticated WordPress user with administrator-level access or higher is required to store the malicious traversal key. The vulnerable behavior affects Events Manager versions through 7.3.7.4.
Does exploitation require a victim to interact with the site after the malicious value is stored?
No. After an administrator stores the malicious key, it is included through include_once() on every admin_init invocation. This includes unauthenticated requests to admin-ajax.php, with no further authentication or capability check required for the inclusion to trigger.
What is required to turn the file inclusion into code execution?
The attacker needs a PHP file on the server that can be included. The issue can enable execution of arbitrary PHP code where PHP file types can be uploaded and then included.