phpMyAdmin Local file inclusion through transformation feature
An attacker can exploit phpMyAdmin before 4.8.4 to leak the contents of a local file because of an error in the transformation feature. The attacker must have access to the phpMyAdmin Configuration Storage tables, although these can easily be created in any database to which the attacker has access. An attacker must have valid credentials to log in to phpMyAdmin; this vulnerability does not allow an attacker to circumvent the login system.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | phpmyadmin/phpmyadmin | < 4.8.4 | 4.8.4 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2018-19968
- https://github.com/phpmyadmin/phpmyadmin/commit/6a1ba61e29002f0305a9322a8af4eaaeb11c0732
- https://github.com/phpmyadmin/composer
- https://lists.debian.org/debian-lts-announce/2019/02/msg00003.html
- https://security.gentoo.org/glsa/201904-16
- https://www.phpmyadmin.net/security/PMASA-2018-6
- http://www.securityfocus.com/bid/106178
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-200- Platform
- Composer
- Package
phpmyadmin/phpmyadmin- Disclosed
- 14.05.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-xc97-r49q-cxgc - CC BY 4.0
Vulnerability history: phpmyadmin/phpmyadmin
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 107
- First → latest
- 01.2020 01.2025
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 10
- High 28
- Medium 56
- Low 13
Disclosures per year
- 2020: 1
- 2021: 0
- 2022: 103
- 2023: 2
- 2024: 0
- 2025: 1
- 2026: 0
-
phpMyAdmin Local file inclusion through transformation feature this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.