CVE-2016-6611
Last modified
CVE-2016-6611 is a vulnerability of currently unknown severity. An issue was discovered in phpMyAdmin. A specially crafted database and/or table name can be used to trigger an SQL injection attack through the export functionality. EPSS estimates a 1.57% chance of exploitation in the next 30 days.
Description
An issue was discovered in phpMyAdmin. A specially crafted database and/or table name can be used to trigger an SQL injection attack through the export functionality. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Phpmyadmin | Phpmyadmin | 4.0.0 |
| Phpmyadmin | Phpmyadmin | 4.0.1 |
| Phpmyadmin | Phpmyadmin | 4.0.2 |
| Phpmyadmin | Phpmyadmin | 4.0.3 |
| Phpmyadmin | Phpmyadmin | 4.0.4 |
| Phpmyadmin | Phpmyadmin | 4.0.4.1 |
| Phpmyadmin | Phpmyadmin | 4.0.4.2 |
| Phpmyadmin | Phpmyadmin | 4.0.5 |
| Phpmyadmin | Phpmyadmin | 4.0.6 |
| Phpmyadmin | Phpmyadmin | 4.0.7 |
| Phpmyadmin | Phpmyadmin | 4.0.8 |
| Phpmyadmin | Phpmyadmin | 4.0.9 |
| Phpmyadmin | Phpmyadmin | 4.0.10 |
| Phpmyadmin | Phpmyadmin | 4.0.10.1 |
| Phpmyadmin | Phpmyadmin | 4.0.10.2 |
| Phpmyadmin | Phpmyadmin | 4.0.10.3 |
| Phpmyadmin | Phpmyadmin | 4.0.10.4 |
| Phpmyadmin | Phpmyadmin | 4.0.10.5 |
| Phpmyadmin | Phpmyadmin | 4.0.10.6 |
| Phpmyadmin | Phpmyadmin | 4.0.10.7 |
| Phpmyadmin | Phpmyadmin | 4.0.10.8 |
| Phpmyadmin | Phpmyadmin | 4.0.10.9 |
| Phpmyadmin | Phpmyadmin | 4.0.10.10 |
| Phpmyadmin | Phpmyadmin | 4.0.10.11 |
| Phpmyadmin | Phpmyadmin | 4.0.10.12 |
| Phpmyadmin | Phpmyadmin | 4.0.10.13 |
| Phpmyadmin | Phpmyadmin | 4.0.10.14 |
| Phpmyadmin | Phpmyadmin | 4.0.10.15 |
| Phpmyadmin | Phpmyadmin | 4.0.10.16 |
| Phpmyadmin | Phpmyadmin | 4.4.0 |
| Phpmyadmin | Phpmyadmin | 4.4.1 |
| Phpmyadmin | Phpmyadmin | 4.4.1.1 |
| Phpmyadmin | Phpmyadmin | 4.4.2 |
| Phpmyadmin | Phpmyadmin | 4.4.3 |
| Phpmyadmin | Phpmyadmin | 4.4.4 |
| Phpmyadmin | Phpmyadmin | 4.4.5 |
| Phpmyadmin | Phpmyadmin | 4.4.6 |
| Phpmyadmin | Phpmyadmin | 4.4.6.1 |
| Phpmyadmin | Phpmyadmin | 4.4.7 |
| Phpmyadmin | Phpmyadmin | 4.4.8 |
| Phpmyadmin | Phpmyadmin | 4.4.9 |
| Phpmyadmin | Phpmyadmin | 4.4.10 |
| Phpmyadmin | Phpmyadmin | 4.4.11 |
| Phpmyadmin | Phpmyadmin | 4.4.12 |
| Phpmyadmin | Phpmyadmin | 4.4.13 |
| Phpmyadmin | Phpmyadmin | 4.4.13.1 |
| Phpmyadmin | Phpmyadmin | 4.4.14.1 |
| Phpmyadmin | Phpmyadmin | 4.4.15 |
| Phpmyadmin | Phpmyadmin | 4.4.15.1 |
| Phpmyadmin | Phpmyadmin | 4.4.15.2 |
Showing 50 of 59 affected configurations. See NVD for the full list.
References
- https://www.phpmyadmin.net/security/PMASA-2016-34Patch, Vendor Advisory
- https://www.phpmyadmin.net/security/PMASA-2016-34Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-6611?
How severe is CVE-2016-6611?
How do I fix CVE-2016-6611?
Are you affected by CVE-2016-6611?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
