Renamed login slug behaviour
-
Hi
In instances where the default WordPress login slug has been renamed to hide it from brute force attacks (eg. login page renamed to example.com/letmein), and with this Password Protected plugin enabled, some elements of the site are revealed to anyone appending ‘/wp-login.php’ to the domain (eg. example.com/wp-login.php). While page content isn’t displayed (reports a 404), the site styling, banner/header area and its contents such as menu(s) and search feature, and also the footer area, are revealed to the visitor.
Just reporting the above as not sure if it’s known/by-design behaviour. A 301 redirect on /wp-login.php back to the home url resolves the problem, presenting the visitor with the password protected login screen.
WordPress 6.2.2
Password Protected: 2.6.3.1
- The topic ‘Renamed login slug behaviour’ is closed to new replies.