CVE-2019-6799

CVE-2019-6799 is a medium-severity vulnerability in Phpmyadmin with a CVSS 3.x base score of 5.9. Its EPSS exploit-prediction score of 16% places it in the 96th percentile, indicating an elevated likelihood of exploitation.

Key facts

Description

An issue was discovered in phpMyAdmin before 4.8.5. When the AllowArbitraryServer configuration setting is set to true, with the use of a rogue MySQL server, an attacker can read any file on the server that the web server's user can access. This is related to the mysql.allow_local_infile PHP configuration, and the inadvertent ignoring of "options(MYSQLI_OPT_LOCAL_INFILE" calls.

Frequently asked questions

What is CVE-2019-6799?
An issue was discovered in phpMyAdmin before 4.8.5. When the AllowArbitraryServer configuration setting is set to true, with the use of a rogue MySQL server, an attacker can read any file on the server that the web server's user can access. This is related to the mysql.allow_local_infile PHP configuration, and the inadvertent ignoring of "options(MYSQLI_OPT_LOCAL_INFILE" calls.
How severe is CVE-2019-6799?
CVE-2019-6799 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-6799 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 16% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-6799?
CVE-2019-6799 primarily affects Phpmyadmin. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-6799?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-6799 published?
CVE-2019-6799 was published on 2019-01-26 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Phpmyadmin

All CVEs affecting Phpmyadmin →