Is wps-hide-login (WordPress plugin) vulnerable?

WordPress wps-hide-login has 9 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

9advisories
4critical
0on CISA KEV
1no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2021-24917The WPS Hide Login WordPress plugin before 1.9.1 has a bug which allows to get the secret login page by setting a random referer string and high7.5<1.9.11.9.1
CVE-2019-15823The wps-hide-login plugin before 1.5.3 for WordPress has an action=confirmaction protection bypass.critical9.8<1.5.31.5.3
CVE-2019-15824The wps-hide-login plugin before 1.5.3 for WordPress has an adminhash protection bypass.critical9.8<1.5.31.5.3
CVE-2019-15825The wps-hide-login plugin before 1.5.3 for WordPress has an action=rp&key&login protection bypass.critical9.8<1.5.31.5.3
CVE-2019-15826The wps-hide-login plugin before 1.5.3 for WordPress has a protection bypass via wp-login.php in the Referer field.critical9.8<1.5.31.5.3
CVE-2024-2473The WPS Hide Login plugin for WordPress is vulnerable to Login Page Disclosure in all versions up to, and including, 1.9.15.2. This is due tmedium5.3<1.9.161.9.16
CVE-2024-6289The WPS Hide Login WordPress plugin before 1.9.16.4 does not prevent redirects to the login page via the auth_redirect WordPress function, amedium6.1<1.9.16.41.9.16.4
CVE-2020-36710The WPS Hide Login plugin for WordPress is vulnerable to login page disclosure even when the settings of the plugin are set to hide the logimedium5.3<=1.5.4.2–
CVE-2015-9498The wps-hide-login plugin before 1.1 for WordPress has CSRF that affects saving an option value.high8.8<1.11.1

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.