Events Made Easy Contributors can store a local-file-inclusion payload
Events Made Easy through 3.2.5 lets a Contributor or higher store a traversal value that reaches the eme_single_event_page_template function. When any visitor opens the affected single-event page, the stored value can include and execute an arbitrary PHP file already present on the server. This can expose local data, bypass access controls or execute the PHP file's code; obtaining a suitable PHP file is an additional prerequisite where one is not already available.
- Component
- Events Made Easy
- Plugin slug
events-made-easy- Affected
- <= 3.2.5
- Safe version
3.2.6- Published
- Aug 20, 2026
This CVE was published Aug 20, 2026 and is one of 10 known issues for this plugin.
Update, patch or deactivate.
Update Events Made Easy to 3.2.6 or later. The official 3.2.6 changelog explicitly identifies its fix for CVE-2026-75963. Review Contributor-authored event templates and unexpected PHP files, and investigate privileged activity if an affected event page may have been triggered.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Events Made Easy plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.5 via the eme_single_event_page_template function. This makes it possible for authenticated attackers, with contributor-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 payload is triggered passively when any visitor loads the affected single-event page, meaning post-submission execution does not require additional attacker interaction.
CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H