When was CVE-2016-2038 disclosed?

CVE-2016-2038 was first published in the National Vulnerability Database on February 20, 2016, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2016-2038 actively exploited?

CVE-2016-2038 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 79.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2016-2038?

CVE-2016-2038 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2016-2038?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2038, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

CVE-2016-2038

MEDIUMNVD 5.35.3—

5.3

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 allows remote attackers to obtain sensitive information via a crafted request, which reveals the full path in an error message.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 79.3%
KEV: Not listed

References (22)

cve@mitrehttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/176483.html
cve@mitrehttp://lists.fedoraproject.org/pipermail/package-announce/2016-February/176739.html
cve@mitrehttp://lists.opensuse.org/opensuse-updates/2016-02/msg00028.html
cve@mitrehttp://lists.opensuse.org/opensuse-updates/2016-02/msg00049.html
cve@mitrehttp://www.phpmyadmin.net/home_page/security/PMASA-2016-1.php
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/447c88f4884fe30a25d38c331c31d820a19f8c93
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/5aee5035646c4fc617564cb0d3d58c0435d64d81
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/76b10187c38634a29d6780f99f6dcd796191073b
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/85ccdbb5b9c6c7a9830e5cb468662837a59a7aa3
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/d4b9c22c1f8465bda5b6a83dc7e2cf59c3fe44e1
cve@mitrehttps://github.com/phpmyadmin/phpmyadmin/commit/f83b52737e321005959497d8e8f59f8aaedc9048
af854a3a-2127-422b-91ae-364da2661108http://lists.fedoraproject.org/pipermail/package-announce/2016-February/176483.html
af854a3a-2127-422b-91ae-364da2661108http://lists.fedoraproject.org/pipermail/package-announce/2016-February/176739.html
af854a3a-2127-422b-91ae-364da2661108http://lists.opensuse.org/opensuse-updates/2016-02/msg00028.html
af854a3a-2127-422b-91ae-364da2661108http://lists.opensuse.org/opensuse-updates/2016-02/msg00049.html

Is Your Infrastructure Affected by CVE-2016-2038?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2016-2038

Published

Last Modified

References (22)

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2016-2038?

CVE-2016-2038

📅 Published

🔄 Last Modified

🔗 References (22)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2016-2038?

Published

Last Modified

References (22)

Frequently asked(5)