p PatchFirst

PatchFirst · Latest vulnerabilities

phpmyadmin/phpmyadmin vulnerabilities · Page 2

Vulnerabilities published for phpmyadmin/phpmyadmin in the last 30 days: 0. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 107

  1. CVE-2018-19969

    High · CVSS 8.8EPSS 1.06%Fix available

    CVE-2018-19969

    phpMyAdmin 4.7.x and 4.8.x versions prior to 4.8.4 are affected by a series of CSRF flaws. By deceiving a user into clicking on a crafted URL, it is possible to perform harmful SQL operations such as renaming databases, creating new tables/routines, deleting designer pages, adding/deleting users, updating user passwords, killing SQL processes, etc.

    • Update to 4.8.4
    Published Updated
  2. CVE-2018-19968

    Medium · CVSS 6.5EPSS 2.89%Fix available

    CVE-2018-19968

    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.

    • Update to 4.8.4
    Published Updated
  3. CVE-2018-12613

    High · CVSS 8.8EPSS 98.35%Public exploitFix available

    CVE-2018-12613

    An 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 server. The vulnerability comes from a portion of code where pages are redirected and loaded within phpMyAdmin, and an improper test for whitelisted pages. An attacker must be authenticated, except in the "$cfg['AllowArbitraryServer'] = true" case (where an attacker can specify any host he/she is already in control of, and execute arbitrary code on phpMyAdmin) and the "$cfg['ServerDefault'] = 0" case (which bypasses the login requirement and runs the vulnerable code without any authentication).

    • Update to 4.8.2
    Published Updated
  4. CVE-2017-18264

    Critical · CVSS 9.8EPSS 2.82%Fix available

    CVE-2017-18264

    An issue was discovered in libraries/common.inc.php in phpMyAdmin 4.0 before 4.0.10.20, 4.4.x, 4.6.x, and 4.7.0 prereleases. The restrictions caused by $cfg['Servers'][$i]['AllowNoPassword'] = false are bypassed under certain PHP versions (e.g., version 5). This can allow the login of users who have no password set even if the administrator has set $cfg['Servers'][$i]['AllowNoPassword'] to false (which is also the default). This occurs because some implementations of the PHP substr function return false when given '' as the first argument.

    • Update to 4.0.10.20
    • Update to 4.7.0
    Published Updated
  5. CVE-2016-9866

    Critical · CVSS 9.8EPSS 1.03%Fix available

    CVE-2016-9866

    An issue was discovered in phpMyAdmin. When the arg_separator is different from its default & value, the CSRF token was not properly stripped from the return URL of the preference import action. All 4.6.x versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to 4.0.10.18) are affected.

    • Update to 4.0.10.18
    • Update to 4.4.15.9
    • Update to 4.6.5
    Published Updated
  6. CVE-2016-9861

    High · CVSS 7.5EPSS 1.79%Fix available

    CVE-2016-9861

    An issue was discovered in phpMyAdmin. Due to the limitation in URL matching, it was possible to bypass the URL white-list protection. All 4.6.x versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to 4.0.10.18) are affected.

    • Update to 4.0.10.18
    • Update to 4.4.15.9
    • Update to 4.6.5
    Published Updated
  7. CVE-2016-9860

    Medium · CVSS 5.9EPSS 1.93%Fix available

    CVE-2016-9860

    An issue was discovered in phpMyAdmin. An unauthenticated user can execute a denial of service attack when phpMyAdmin is running with $cfg['AllowArbitraryServer']=true. All 4.6.x versions (prior to 4.6.5), 4.4.x versions (prior to 4.4.15.9), and 4.0.x versions (prior to 4.0.10.18) are affected.

    • Update to 4.0.10.18
    • Update to 4.4.15.9
    • Update to 4.6.5
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →