Skip to content
Laskyr

Plugins · rename-wp-loginphp-to-anything-you-want · data as of 2026-11-04

Is Rename wp-login.php to anything you want safe? Known vulnerabilities and latest version

Rename wp-login.php to anything you want is closed on wordpress.org

Closed on 2026-09-21. Closed plugins get no updates through WordPress, so new security holes will not be fixed for you.

Status
Closed 2026-09-21
Known issues on record
1
Unpatched in latest
0

What to do

  1. Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
  2. Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
  3. If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate rename-wp-loginphp-to-anything-you-want && wp plugin delete rename-wp-loginphp-to-anything-you-want

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 1 record(s) do not state which versions are affected.

high 7.5 CVE-2026-93368 · published 2026-09-23

SQL injection in Rename wp-login.php to anything you want (2.0.1 and older)

Affected
2.0.1 and older
Fixed in
unknown
Access needed (per CVSS)
No login needed
Range from
CVE record (the advisory publisher) · score by Wordfence
Details from the advisory

The Rename wp-login.php to anything you want plugin for WordPress is vulnerable to time-based SQL Injection via 'log' (Username) Parameter in all versions up to, and including, 2.0.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. WordPress core applies wp_unslash() to the 'log' POST value before dispatching the wp_login_failed action, stripping magic-quotes backslash escaping and allowing a raw single quote to reach the plugin's handler unimpeded.

NVD CVE-2026-93368Wordfence advisoryPlugin source

Recent activity

Browse vulnerabilities

Where this data comes from

Badge for your site or docs (states facts with a date, not a verdict):
Rename wp-login.php to anything you want vulnerability status badge
<a href="https://laskyr.com/plugins/rename-wp-loginphp-to-anything-you-want"><img src="https://laskyr.com/plugins/rename-wp-loginphp-to-anything-you-want/badge.svg" alt="Rename wp-login.php to anything you want vulnerability status"></a>

← Check another plugin · Free hacked-site scan

First hour checklist

If the site was just hacked, read the emergency kit before you delete files. The page is free. Email is optional.

Read the emergency kit