How to fix: WordPress login page publicly accessible
The WordPress admin login page (/wp-login.php or /wp-admin/) is publicly accessible, exposing it to brute-force attacks.
Why it matters
Publicly accessible WordPress login pages are continuously attacked by automated bots attempting credential stuffing and brute-force attacks. A weak admin password will be compromised quickly.
While hiding the login URL provides only obscurity, combining it with rate limiting, 2FA, and IP allowlisting significantly reduces attack surface.
How to fix it
- 1Enable login rate limiting and CAPTCHA
- 2Require two-factor authentication for all admin accounts
- 3Restrict /wp-admin/ access to specific IP ranges at the server level
- 4Keep WordPress and all plugins updated
Code examples
Block wp-login.php in nginx
# nginx.conf: restrict wp-login.php to known admin IPs
location = /wp-login.php {
allow 203.0.113.0/24;
deny all;
}References
Detected automatically by VulnRadar. The check id is wp-login-exposed, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is WordPress login page publicly accessible?
- VulnRadar rates this info severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id wp-login-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does WordPress login page publicly accessible map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.