Is front-end-only-users (WordPress plugin) vulnerable?

WordPress front-end-only-users has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
1critical
0on CISA KEV
2no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2025-2005The Front End Users plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the file uploads fiecritical9.8<=3.2.32–
CVE-2024-7607The Front End Users plugin for WordPress is vulnerable to time-based SQL Injection via the ‘order’ parameter in all versions up to, and inclhigh8.8<3.2.293.2.29
CVE-2024-12410The Front End Users plugin for WordPress is vulnerable to SQL Injection via the 'UserSearchField' parameter in all versions up to, and inclumedium4.9<=3.2.32–
CVE-2024-7606The Front End Users plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'user-search' shortcode in all versiomedium6.4<3.2.293.2.29
CVE-2024-13563The Front End Users plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's forgot-password shortcode in all versmedium6.4<3.2.313.2.31

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.