Is imember360 (WordPress plugin) vulnerable?

WordPress imember360 has 5 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.

5advisories
0critical
0on CISA KEV
5no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2014-3848The iMember360 plugin before 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to obtain database credemedium5.0<=3.9.000–
CVE-2014-8949The iMember360 plugin 3.8.012 through 3.9.001 for WordPress allows remote authenticated administrators to execute arbitrary commands via shemedium6.0=3.8.012 or =3.8.013 or =3.8.014 or =3.9.000 or =3.9.001–
CVE-2014-3849The iMember360 plugin 3.8.012 through 3.9.001 for WordPress does not properly restrict access, which allows remote attackers to delete arbitmedium4.3=3.8.012 or =3.8.013 or =3.8.014 or =3.9.000 or =3.9.001–
CVE-2014-3842Multiple cross-site scripting (XSS) vulnerabilities in the iMember360 plugin 3.8.012 through 3.9.001 for WordPress allow remote attackers tomedium4.3=3.8.012 or =3.8.013 or =3.8.014 or =3.9.000 or =3.9.001–
CVE-2014-8948Cross-site request forgery (CSRF) vulnerability in the iMember360 plugin 3.8.012 through 3.9.001 for WordPress allows remote attackers to himedium6.8=3.8.012 or =3.8.013 or =3.8.014 or =3.9.000 or =3.9.001–

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.

# one-time install
pip install phpwarden

# then
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.