8.1
CWE
89
Advisory Published
Updated

CVE-2016-6617: SQL Injection

First published: Sun Dec 11 2016(Updated: )

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) are affected.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
PhpMyAdmin=4.6.0
PhpMyAdmin=4.6.1
PhpMyAdmin=4.6.2
PhpMyAdmin=4.6.3

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-6617?

    CVE-2016-6617 has been classified as a high severity vulnerability due to its potential to allow SQL injection attacks.

  • How do I fix CVE-2016-6617?

    To fix CVE-2016-6617, upgrade phpMyAdmin to version 4.6.4 or later.

  • Which versions of phpMyAdmin are affected by CVE-2016-6617?

    CVE-2016-6617 affects all phpMyAdmin versions in the 4.6.x series prior to 4.6.4.

  • What type of vulnerability is CVE-2016-6617?

    CVE-2016-6617 is an SQL injection vulnerability that can be exploited through the export functionality.

  • Can CVE-2016-6617 impact my database security?

    Yes, exploiting CVE-2016-6617 can compromise database security by allowing unauthorized access to sensitive data.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203