CVE-2009-1151
KEVphpMyAdmin Remote Code Execution Vulnerability
Description
Setup script used to generate configuration can be fooled using a crafted POST request to include arbitrary PHP code in generated configuration file.
Static code injection vulnerability in setup.php in phpMyAdmin 2.11.x before 2.11.9.5 and 3.x before 3.1.3.1 allows remote attackers to inject arbitrary PHP code into a configuration file via the save action.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HPublishedMar 26, 2009
Last modifiedJun 16, 2026
Added to KEVMar 25, 2022
Remediation dueApr 15, 2022
References
- labs.neohapsis.com/2009/04/06/about-cve-2009-1151/Broken Link
- lists.opensuse.org/opensuse-security-announce/2009-04/msg00003.htmlProduct
- phpmyadmin.svn.sourceforge.net/viewvc/phpmyadmin/branches/MAINT_2_11_9/phpMyAdmin/scripts/setup.php?r1=11514&r2=12301&pathrev=12301Vendor Advisory
- secunia.com/advisories/34430Broken LinkVendor Advisory
- secunia.com/advisories/34642Broken LinkVendor Advisory
- secunia.com/advisories/35585Broken LinkVendor Advisory
- secunia.com/advisories/35635Broken LinkVendor Advisory
- security.gentoo.org/glsa/glsa-200906-03.xmlThird Party Advisory
- debian.org/security/2009/dsa-1824Mailing List
- gnucitizen.org/blog/cve-2009-1151-phpmyadmin-remote-code-execution-proof-of-concept/ExploitIssue Tracking
- mandriva.com/security/advisories?name=MDVSA-2009:115Broken Link
- phpmyadmin.net/home_page/security/PMASA-2009-3.phpPatchVendor Advisory
0 recent articles mention this CVE
89
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 1655 days
- CVSS
- 9.8 CRITICAL
- EPSS (30-day exploit probability)
- 96.6% · top 1% of all CVEs
- Weakness
- CWE-94
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
Recommended actions
- 1.Apply updates per vendor instructions.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.