S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated Jan 21, 2026

CVE-2020-26935 Scanner

Targets the SQL query parameter in phpMyAdmin's table search functionality, allowing attackers to execute arbitrary SQL commands and extract sensitive database contents.

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
3.4k
Times Used
continuous scan runs
4.7k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2020-26935
9.8
CVSS

An issue was discovered in SearchController in phpMyAdmin before 4.9.6 and 5.x before 5.0.3. A SQL injection vulnerability was discovered in how phpMyAdmin processes SQL statements in the search feature. An attacker could use this flaw to inject malicious SQL in to a query.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
n/aby n/a
n/a
Updated Aug 21, 2026View on NVD →
Detail

phpMyAdmin is a widely used web-based application for managing MySQL databases, primarily utilized by web developers and database administrators. It provides a graphical interface for interacting with databases, creating, modifying, and deleting records, tables, and overall database management. phpMyAdmin is extensively used in web hosting environments and local development setups, facilitating easier database management. It supports most MySQL features, including import and export of data and managing multiple databases. The application is commonly embedded into web hosting control panels like cPanel for easier access for users. Given its comprehensive feature set, phpMyAdmin remains a key tool for database management in various web applications and environments.

CVE-2020-26935 is a critical SQL injection vulnerability in phpMyAdmin versions prior to 4.9.6 and 5.0.3. The flaw arises due to insufficient sanitization of user-supplied input within the table search functionality. Attackers can inject malicious SQL code through crafted parameters, bypassing intended query constraints. This vulnerability is classified as pre-authentication in some scenarios, meaning exploitation does not require valid credentials, significantly increasing its severity. The root cause is the lack of proper escaping or parameterized queries in the affected code path, allowing direct manipulation of SQL statements.

Specifically, the vulnerability exists in the 'tbl_find_replace' and 'tbl_sql' scripts where user input from the 'find' parameter is directly concatenated into SQL queries without adequate validation. An attacker can send a specially crafted HTTP request to the phpMyAdmin interface, targeting the table search endpoint. By injecting SQL commands into the 'find' parameter, they can alter the intended query logic. For example, appending a UNION SELECT statement can retrieve data from other tables. The exploit does not require authentication if the phpMyAdmin instance is exposed to the internet, making it a high-risk vector for data breaches.

If successfully exploited, an attacker can gain unauthorized access to all databases managed by the phpMyAdmin instance. This includes reading sensitive data such as user credentials, personal information, and financial records. The attacker can also modify or delete database contents, leading to data integrity loss or service disruption. In worst-case scenarios, the attacker might escalate privileges to execute operating system commands via MySQL's INTO OUTFILE feature, potentially compromising the entire server. Given the CVSS score of 9.8, this vulnerability poses a critical threat to any organization using affected phpMyAdmin versions, requiring immediate remediation.

Solution Advice
  • Update phpMyAdmin to version 4.9.6, 5.0.3, or the latest available version to patch CVE-2020-26935.
  • Implement parameterized queries or prepared statements in all database interactions to prevent SQL injection.
  • Restrict access to phpMyAdmin by IP whitelisting or using VPNs to limit exposure to trusted networks.
  • Deploy a Web Application Firewall (WAF) with rules to detect and block SQL injection patterns in requests.
  • Enable detailed logging and monitoring for phpMyAdmin to identify and respond to suspicious activities promptly.
  • Conduct regular security audits and vulnerability scans to identify and remediate similar issues proactively.
  • Disable or remove unused phpMyAdmin features, such as table search, if not required to reduce attack surface.
  • Educate developers and administrators on secure coding practices, emphasizing input validation and safe SQL handling.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.

phpMyAdmin SQL Injection Scanner | S4E Free Check