VDB

CVE-2016-6617

CVE-2016-6617 PUBLISHED

Reported by mitre · Published December 11, 2016

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.

Affected products

VendorProductVersions
n/an/an/a
n/an/a*
alpinephpmyadmin0

Timeline

  • Dec 11, 2016 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Apr 2, 2026 Security Advisory (2 in total, the first dated here)
  • Sep 20, 2026 CVE Updated
  • Oct 7, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-6617
vulnetix vdb fixes CVE-2016-6617

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-6617/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • 95044 vdb-entryx_refsource_BID
  • GLSA-201701-32 vendor-advisoryx_refsource_GENTOO
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›