Is events-made-easy (WordPress plugin) vulnerable?

WordPress events-made-easy has 5 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

5advisories
1critical
0on CISA KEV
2no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2022-1905The Events Made Easy WordPress plugin before 2.2.81 does not properly sanitise and escape a parameter before using it in a SQL statement viacritical9.8<2.2.812.2.81
CVE-2021-25030The Events Made Easy WordPress plugin before 2.2.36 does not sanitise and escape the search_text parameter before using it in a SQL statemenhigh8.8<2.2.362.2.36
CVE-2023-28660The Events Made Easy WordPress Plugin, version <= 2.3.14 is affected by an authenticated SQL injection vulnerability in the 'search_name' pahigh8.8<=2.3.14–
CVE-2021-24813The Events Made Easy WordPress plugin before 2.2.24 does not sanitise and escape Custom Field Names, allowing high privilege users to performedium4.8<2.2.242.2.24
CVE-2023-0404The Events Made Easy plugin for WordPress is vulnerable to authorization bypass due to a missing capability check on several functions relatmedium5.4<=2.3.16–

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.