How to fix: phpMyAdmin Login Page Publicly Reachable
The phpMyAdmin login page renders directly for unauthenticated requests, with no network-level access restriction in front of it.
Why it matters
A public phpMyAdmin login page is a well-known target for credential stuffing and CVE exploitation, and any successful compromise gives an attacker direct SQL access to the database.
phpMyAdmin is an administrative tool intended for trusted operators only. Publishing its login form to the open internet, even with strong credentials, exposes it to brute-force attempts and any un-patched authentication-bypass or RCE vulnerabilities in the installed version.
How to fix it
- 1Restrict access to phpMyAdmin by source IP allowlist or place it behind a VPN.
- 2Add a second layer of authentication (HTTP Basic Auth at the web-server level) in front of the phpMyAdmin path.
- 3Keep the phpMyAdmin installation patched to the latest version.
Code examples
Nginx: restrict by IP
location /phpmyadmin {
allow 203.0.113.10;
deny all;
}References
Detected automatically by VulnRadar. The check id is phpmyadmin-login-exposed, stable across every scan so you can filter or diff on it.
More config checks
- MediumNo Rate-Limit Policy Detected
- MediumVary: Cookie Missing on Cookie-Bearing Response
- LowSet-Cookie Header Exceeds 4 KB
- LowVary Header Missing on Compressed Responses
- InfoDownloadable Content Served as inline
- InfoX-XSS-Protection Header Is Deprecated
- LowServer-Timing Exposes Cache Timings
- LowVary: Cookie on Static Resource
Questions
- How severe is phpMyAdmin Login Page Publicly Reachable?
- VulnRadar rates this high severity in the config 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 phpmyadmin-login-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does phpMyAdmin Login Page Publicly Reachable map to?
- It maps to CWE-284. 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.