Loading vulnerability…
CVE-2020-5504 is an SQL injection vulnerability in the phpMyAdmin user accounts page affecting phpMyAdmin versions before 4.9.4 in the 4.x branch and versions before 5.0.1 in the 5.x branch. A malicious authenticated user can supply custom SQL in place of their own username when phpMyAdmin creates queries for the user accounts page.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a standalone Python-based exploitation/assessment tool for CVE-2020-5504 in phpMyAdmin, not part of a larger exploit framework. The main logic resides in exploit.py, which implements a structured assessment workflow with multiple modes: detect, verify, research, and dry-run. The code defines scan configuration, fingerprinting, authentication, response analysis, verification status tracking, and report generation. Based on the visible code and README, its primary capabilities are: identifying phpMyAdmin instances, attempting authenticated access with supplied credentials, checking whether the target appears vulnerable, and optionally performing broader database-oriented research/extraction under configurable limits such as max_databases, max_tables, max_columns, max_rows, and max_value_length. Repository structure is simple: exploit.py is the main entry point; requirements.txt lists Python dependencies (requests, rich, colorama, dataclasses backport); start.sh, start.ps1, and start.bat are convenience launchers for Linux/macOS, PowerShell, and Windows CMD respectively. These wrappers handle Python detection, optional virtual environment setup, dependency installation, interactive collection of target URL/credentials/proxy/output settings, and execution of exploit.py. The exploit is web-based and targets phpMyAdmin over HTTP(S). It accepts a user-supplied target URL rather than hardcoding victim infrastructure. The README states the vulnerability affects phpMyAdmin 4.x before 4.9.4 and 5.0.0 / fixed in 5.0.1 for the 5.x line, and notes that valid MySQL/phpMyAdmin credentials are required. The tool appears operational rather than a minimal PoC because it includes authentication handling, configurable scan limits, retry/timeout/proxy support, response analysis, and reporting. No obviously destructive fake behavior is present. The startup scripts also expose potentially unsafe local behavior via custom command execution options, but that is launcher functionality rather than the exploit payload itself.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.