The Events Made Easy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'width' parameter in all versions up to, and including, 3.3.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contri...
Product
wordpress events-made-easy vulnerabilities
14 published CVES affecting wordpress events-made-easy, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 14
- Critical
- 1
- High
- 5
- Medium
- 8
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress events-made-easy CVEs
Newest publication first
-
MediumCVSS 6.4 EPSS 0.20%
-
MediumCVSS 5.4 EPSS 0.22%
The Events Made Easy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event[location_name]' parameter in all versions up to, and including, 3.2.22 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated atta...
-
CVE-2026-28162 WordPress Events Made Easy plugin <= 3.2.5 - Cross Site Scripting (XSS) vulnerability
PublishedHighCVSS 7.1 EPSS 0.25%Unauthenticated Cross Site Scripting (XSS) in Events Made Easy <= 3.2.5 versions.
-
HighCVSS 7.5 EPSS 0.87%
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...
-
MediumCVSS 5.3 EPSS 0.30%
The Events Made Easy WordPress plugin before 3.1.2 does not bind the payment authorization token to the payment record being charged, allowing unauthenticated attackers to pay a low amount for a cheap booking and have a separate, higher-priced booking marked as fully paid.
-
CVE-2026-14843 Events Made Easy < 3.1.4 - Unauthenticated Person Data Modification via IDOR
PublishedMediumCVSS 5.3 EPSS 0.30%The Events Made Easy WordPress plugin before 3.1.4 does not verify that the requester is authorized to modify the targeted record when handling an unauthenticated data-change request, relying only on a public nonce with no per-record token or ownership check, allowing unauthentic...
-
CVE-2026-59557 WordPress Events Made Easy plugin <= 3.1.3 - Broken Access Control vulnerability
PublishedMediumCVSS 6.5 EPSS 0.33%Unauthenticated Broken Access Control in Events Made Easy <= 3.1.3 versions.
-
HighCVSS 8.8 EPSS 0.87%
The Events Made Easy WordPress Plugin, version <= 2.3.14 is affected by an authenticated SQL injection vulnerability in the 'search_name' parameter in the eme_recurrences_list action.
-
MediumCVSS 5.4 EPSS 0.56%
The Events Made Easy plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on several functions related to AJAX actions in versions up to, and including, 2.3.16. This makes it possible for authenticated attackers, with subscriber-level permi...
-
CriticalCVSS 9.8 EPSS 37.1%
The Events Made Easy WordPress plugin before 2.2.81 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection
-
HighCVSS 8.8 EPSS 1.4%
The Events Made Easy WordPress plugin before 2.2.36 does not sanitise and escape the search_text parameter before using it in a SQL statement via the eme_searchmail AJAX action, available to any authenticated users. As a result, users with a role as low as subscriber can call it...
-
MediumCVSS 4.8 EPSS 0.70%
The Events Made Easy WordPress plugin before 2.2.24 does not sanitise and escape Custom Field Names, allowing high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed
-
MediumCVSS 6.1
The Events Made Easy plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting via the 'page' parameter in versions up to, and including, 1.6.20 due to insufficient input sanitization and output escaping. This makes it possible for attackers...
-
HighCVSS 8.8
The Events Made Easy plugin for WordPress is vulnerable to Cross-Site Request Forgery to Stored Cross-Site Scripting in versions before 1.5.50 due to insufficient input sanitization and output escaping and missing nonce validation. This makes it possible for attackers to inject a...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.