Show filters
273 Total Results
Displaying 21-30 of 273
Sort by:
Attacker Value
Unknown

CVE-2019-12922

Disclosure Date: September 13, 2019 (last updated November 08, 2023)
A CSRF issue in phpMyAdmin 4.9.0.1 allows deletion of any server in the Setup page.
Attacker Value
Unknown

CVE-2019-11768

Disclosure Date: June 05, 2019 (last updated November 08, 2023)
An issue was discovered in phpMyAdmin before 4.9.0.1. A vulnerability was reported where a specially crafted database name can be used to trigger an SQL injection attack through the designer feature.
0
Attacker Value
Unknown

CVE-2019-12616

Disclosure Date: June 05, 2019 (last updated November 08, 2023)
An issue was discovered in phpMyAdmin before 4.9.0. A vulnerability was found that allows an attacker to trigger a CSRF attack against a phpMyAdmin user. The attacker can trick the user, for instance through a broken <img> tag pointing at the victim's phpMyAdmin database, and the attacker can potentially deliver a payload (such as a specific INSERT or DELETE statement) to the victim.
0
Attacker Value
Unknown

CVE-2019-6798

Disclosure Date: January 26, 2019 (last updated November 27, 2024)
An issue was discovered in phpMyAdmin before 4.8.5. A vulnerability was reported where a specially crafted username can be used to trigger a SQL injection attack through the designer feature.
0
Attacker Value
Unknown

CVE-2019-6799

Disclosure Date: January 26, 2019 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown

CVE-2018-19968

Disclosure Date: December 11, 2018 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown

CVE-2018-19970

Disclosure Date: December 11, 2018 (last updated November 27, 2024)
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 through a crafted database/table name.
0
Attacker Value
Unknown

CVE-2018-19969

Disclosure Date: December 11, 2018 (last updated November 27, 2024)
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.
0
Attacker Value
Unknown

CVE-2018-15605

Disclosure Date: August 24, 2018 (last updated November 27, 2024)
An issue was discovered in phpMyAdmin before 4.8.3. A Cross-Site Scripting vulnerability has been found where an attacker can use a crafted file to manipulate an authenticated user who loads that file through the import feature.
0
Attacker Value
Unknown

CVE-2018-12613

Disclosure Date: June 21, 2018 (last updated November 26, 2024)
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).