Phpmyadmin Hacktricks Verified Link

| Aspect | Summary | |--------|---------| | Primary risk | Credential theft → full database compromise → RCE | | Most common mistake | Public exposure + weak root password | | Most powerful feature for attackers | INTO OUTFILE + LOAD_FILE | | Mitigation priority | Restrict network access + update regularly |

| Attack | Mitigation | |--------|-------------| | File write RCE | Set secure_file_priv = "/tmp/" or empty string? Better to set a safe directory or NULL. | | General log injection | Monitor general_log variable changes; set read-only for web user. | | Brute force | Use $cfg['LoginCookieValidity'] = 900 + fail2ban on /phpmyadmin. | | LFI (old versions) | Upgrade to 5.2.1+; remove /doc/ and /changelog.php from production. | phpmyadmin hacktricks verified

Look for /phpmyadmin/themes/pmahomme/img/logo_left.png. Combined with doc/html/index.html or README, you can extract the exact version. Version matters because exploits differ widely between 2.x, 3.x, 4.x, and 5.x. | Aspect | Summary | |--------|---------| | Primary

HackTricks Tip: Use whatweb target.com/phpmyadmin – it often extracts version from meta generators. | Attack | Mitigation | |--------|-------------| | File

Though rare in recent versions, older phpMyAdmin releases had SQL injection vulnerabilities in its own interface (e.g., CVE-2015-2208, CVE-2016-6628).
Attackers could bypass login or execute arbitrary queries without valid credentials.