Skip to content
Fencer Vulns
high 8.8

CVE-2018-10188 json

phpMyAdmin CSRF vulnerability allowing arbitrary SQL execution

published 2018-04-19 8 y ago modified 2026-06-17 4 mo ago also GHSA-v6fp-h79x-9rqc , EUVD-2022-5295

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.1%
EPSS 4.1% chance of exploitation in 30 days, percentile 90%
public exploits
1
Exploit-DB

Summary

phpMyAdmin 4.8.0 before 4.8.0-1 has CSRF, allowing an attacker to execute arbitrary SQL statements, related to js/db_operations.js, js/tbl_operations.js, libraries/classes/Operations.php, and sql.php.

Patch / fix

  • packagist phpmyadmin/phpmyadmin 4.8.0.1
  • phpmyadmin Debian 14, Debian 13, Debian 12 4:4.9.1+dfsg1-2

debian advisories DEBIAN-CVE-2018-10188

  • phpMyAdmin openSUSE Tumbleweed 5.1.1-1.2
  • phpMyAdmin Package Hub 12 4.8.0.1-20.1

opensuse advisories openSUSE-SU-2024:11171-1openSUSE-SU-2018:1058-1openSUSE-SU-2018:1059-1

  • phpmyadmin Alpine 3.24, Alpine 3.23, Alpine 3.22 +3 more 4.8.0-r1

alpine advisories ALPINE-CVE-2018-10188

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Timeline

  1. Published
  2. First public exploit (EDB-44496)

Exploit prediction

4.06% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-44496 phpMyAdmin 4.8.0 < 4.8.0-1 - Cross-Site Request Forgery webapps, 2018-04-23

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist phpmyadmin/phpmyadmin
>=4.8, <4.8.0.1
4.8.0.1

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.