Is community-events (WordPress plugin) vulnerable?

WordPress community-events has 4 known advisories in the phpwarden feed. Feed 2026.10.29.2, updated 2026-10-29.

4advisories
1critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2015-3313SQL injection vulnerability in WordPress Community Events plugin before 1.4.critical9.8<=1.3.5–
CVE-2021-24496The Community Events WordPress plugin before 1.4.8 does not sanitise, validate or escape its importrowscount and successimportcount GET paramedium6.1<1.4.81.4.8
CVE-2024-6270The Community Events WordPress plugin before 1.5.1 does not sanitise and escape some of its settings, which could allow high privilege usersmedium4.8<1.5.11.5.1
CVE-2024-6271The Community Events WordPress plugin before 1.5 does not have CSRF check in place when deleting events, which could allow attackers to makemedium5.4<1.51.5

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.