Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

rename wp-login vulnerabilities and fixes

Recent CVEs affecting rename wp-login, with upgrade or downgrade steps. 1 tracked.

Also searched as: rename wp login, renamewp-login.

rename wp-login has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2022-07-11. Highest priority: CVE-2022-1732 (score 39/100).

FAQ

How do I fix rename wp-login vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is rename wp-login being exploited right now?

None of the tracked rename wp-login CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which rename wp-login CVE should I patch first?

CVE-2022-1732 currently ranks highest (39/100): The Rename wp-login.php WordPress plugin through 2.6.0 does not have CSRF check in place when updating the sec.

← Back to latest CVEs