LiveActive security incident?Get immediate response
CVE Record

CVE-2016-6620: An issue was discovered in phpMyAdmin.

An issue was discovered in phpMyAdmin. Some data is passed to the PHP unserialize() function without verification that it's valid serialized data. The unserialization can result in code execution because of the interaction with object instantiation and autoloading. 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-6620 affects legacy phpMyAdmin releases. Unchecked data can reach PHP unserialize(), which may allow code execution through object creation and autoloading. Organizations still running the listed old branches should treat this as a serious legacy exposure, especially if phpMyAdmin is reachable from untrusted networks. Exposure is limited to phpMyAdmin deployments on the affected legacy branches: 4.6.x before 4.6.4, 4.4.x before 4.4.15.8, and 4.0.x before 4.0.10.17. Internet-facing or broadly accessible administrative phpMyAdmin instances carry higher business risk. Prioritize remediation where phpMyAdmin is internet-facing, shared across teams, or connected to sensitive databases. The issue is old, but legacy administrative tools often persist unnoticed. Treat confirmed affected deployments as high priority for upgrade or retirement. Mitigation focus: Upgrade phpMyAdmin to 4.6.4, 4.4.15.8, 4.0.10.17, or later supported releases.; Apply Debian or Gentoo security package updates where those distributions manage phpMyAdmin.; Restrict phpMyAdmin access to trusted administrative networks or VPN paths..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-6620 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.