CVE-2016-6617

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.

Published: 2016-12-11 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-6617 is rated Moderate Risk (51.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.31%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-6617

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-27 0.39% 0.31% -0.08%
2 2025-03-30 1.33% 0.39% -0.94%
3 2025-03-29 — 1.33% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-6617

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2016-6617

OS Trackers for CVE-2016-6617

vendor priority summary link
debian not yet assigned CVE-2016-6617 not yet assigned priority: Debian including 1 source packages (phpmyadmin), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): resolved 4. https://security-tracker.debian.org/tracker/CVE-2016-6617
gentoo normal CVE-2016-6617: 1 GLSA(s) (201701-32), 1 atom(s) (dev-db/phpmyadmin); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-6617
ubuntu medium CVE-2016-6617 medium priority: Ubuntu including 1 source packages (phpmyadmin), 4 status rows across 4 suites (precise, trusty, upstream, xenial): not-affected 3, released 1. https://ubuntu.com/security/CVE-2016-6617

Affected software / configurations for CVE-2016-6617

Vendor Product Version Raw CPE
phpmyadmin phpmyadmin 4.6.0 cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.0:*:*:*:*:*:*:*
phpmyadmin phpmyadmin 4.6.1 cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.1:*:*:*:*:*:*:*
phpmyadmin phpmyadmin 4.6.2 cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.2:*:*:*:*:*:*:*
phpmyadmin phpmyadmin 4.6.3 cpe:2.3:a:phpmyadmin:phpmyadmin:4.6.3:*:*:*:*:*:*:*

References for CVE-2016-6617

cvelogic Threat Intelligence