VDB
CVE-2016-2039
CVE-2016-2039
PUBLISHED
Reported by mitre · Published February 20, 2016
libraries/session.inc.php in phpMyAdmin 4.0.x before 4.0.10.13, 4.4.x before 4.4.15.3, and 4.5.x before 4.5.4 does not properly generate CSRF token values, which allows remote attackers to bypass intended access restrictions by predicting a value.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| n/a | n/a | * |
Timeline
- Feb 20, 2016 CVE Published
- Feb 4, 2022 EPSS Score (30 in total, the first dated here)
- Apr 12, 2025 CVE Updated
- Apr 2, 2026 Distribution Patch
- Apr 2, 2026 Security Advisory (4 in total, the first dated here)
- Oct 9, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2016-2039
vulnetix vdb fixes CVE-2016-2039
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-2039/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- x_refsource_CONFIRM
- openSUSE-SU-2016:0378 vendor-advisoryx_refsource_SUSE
- DSA-3627 vendor-advisoryx_refsource_DEBIAN
- openSUSE-SU-2016:0357 vendor-advisoryx_refsource_SUSE
- FEDORA-2016-e55278763e vendor-advisoryx_refsource_FEDORA
- FEDORA-2016-e1fe01e96e vendor-advisoryx_refsource_FEDORA
- x_refsource_CONFIRM
- x_refsource_CONFIRM