An issue was discovered in phpMyAdmin before 4.8.5.
Noroxi assessment
Priority: Monitor (action score 27/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 14.8% (FIRST EPSS); higher than 96.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: phpmyadmin (Debian:12) 4:4.9.1+dfsg1-2; phpmyadmin (Debian:8) 4:4.2.12-2+deb8u5; phpmyadmin/phpmyadmin (Packagist) 4.8.5.
Low priority for now. Upgrade to phpmyadmin (Debian:12) 4:4.9.1+dfsg1-2; phpmyadmin (Debian:8) 4:4.2.12-2+deb8u5; phpmyadmin/phpmyadmin (Packagist) 4.8.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jan 26, 2019
- Updated
- Jun 16, 2026
- EPSS
- 14.8% · 96th percentile
- CWE
- —
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 4 / 30 · 14.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phpmyadmin | phpmyadmin | cpe:2.3:a:phpmyadmin:phpmyadmin |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- phpmyadmin phpmyadmin4.0.0 and later · up to 4.8.4 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | phpmyadmin | before 4:4.9.1+dfsg1-2 | 4:4.9.1+dfsg1-2 |
| Debian:8 | phpmyadmin | before 4:4.2.12-2+deb8u5 | 4:4.2.12-2+deb8u5 |
| Packagist | phpmyadmin/phpmyadmin | from 4.8 · before 4.8.5 | 4.8.5 |
| SUSE:Package Hub 12 | phpMyAdmin | before 4.8.5-bp150.3.9.1 | 4.8.5-bp150.3.9.1 |
| SUSE:Package Hub 12 | phpMyAdmin | before 4.8.5-bp150.3.9.1 | 4.8.5-bp150.3.9.1 |
Same product
phpmyadmin: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-1151Static code injection vulnerability in setup.php in phpMyAdmin 2.11.x before 2.11.9.5 and 3.x before 3.1.3.1 allows remote attackers to injeKEV98Now
- CVE-2018-12613An issue was discovered in phpMyAdmin 4.8.x before 4.8.2, in which an attacker can include (view and potentially execute) files on the serve65This week
- CVE-2016-5734phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the p63This week
Published before and after this one in the same product
- ← EarlierCVE-2018-19970Dec 11, 2018 · In phpMyAdmin before 4.8.4, an XSS vulnerability was found in the navigation tree, where an attacker can deliver a payload to a user through25Monitor
- ← EarlierCVE-2019-6798Jan 26, 2019 · An issue was discovered in phpMyAdmin before 4.8.5.40Plan
- Later →CVE-2019-11768Jun 5, 2019 · An issue was discovered in phpMyAdmin before 4.9.0.1.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:phpmyadmin | 4:4.9.1+dfsg1-2 · Debian:12 | Package registry (OSV) |
| opensuse:phpMyAdmin | 4.8.5-bp150.3.9.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| Packagist:phpmyadmin/phpmyadmin | 4.8.5 | Package registry (OSV) |
| suse:phpMyAdmin | 4.8.5-bp150.3.9.1 · SUSE:Package Hub 12 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2019-6799 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.