CVE-2009-1151
Published: March 25, 2022
Official Description
Setup script used to generate configuration can be fooled using a crafted POST request to include arbitrary PHP code in generated configuration file.
CISA KEV Advisory
phpMyAdmin Remote Code Execution Vulnerability
Setup script used to generate configuration can be fooled using a crafted POST request to include arbitrary PHP code in generated configuration file.
Apply updates per vendor instructions.
Risk Analysis
A setup script used to generate configuration files can be manipulated via a crafted POST request to include arbitrary PHP code. This allows an attacker to inject malicious code into the generated configuration. The high EPSS score of 0.92956 indicates a very high likelihood of exploitation, making this a critical vulnerability.
This vulnerability has been actively exploited in the wild and is listed in CISA's KEV catalog, confirming its use by malicious actors. The remote nature of the exploit makes it a significant threat.
Administrators should ensure that all setup scripts are secured and updated, and that input validation is strictly enforced for all POST requests. Regularly review generated configuration files for unauthorized modifications.
Technical Analysis
CVE-2009-1151 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2009-1151 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2009-1151 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1