CVE-2018-25161
Published: 06 March 2026
Summary
CVE-2018-25161 is a high-severity SQL Injection (CWE-89) vulnerability. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 13.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Deeper analysis
CVE-2018-25161 is an SQL injection vulnerability (CWE-89) affecting Warranty Tracking System version 11.06.3. The issue exists in the SearchCustomer.php component, where the POST parameters txtCustomerCode, txtCustomerName, and txtPhone are vulnerable to malicious input. This allows attackers to inject arbitrary SQL queries, including crafted UNION SELECT statements, to extract sensitive database information such as usernames, database names, and version details.
The vulnerability carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N), indicating it can be exploited remotely by unauthenticated attackers with low complexity and no user interaction. Exploitation enables remote attackers to execute arbitrary SQL queries, primarily achieving high-impact confidentiality breaches by dumping sensitive data from the database, with low integrity impact and no availability disruption.
References include an Exploit-DB entry (https://www.exploit-db.com/exploits/45881) providing a proof-of-concept for the SQL injection and a Vulncheck advisory (https://www.vulncheck.com/advisories/warranty-tracking-system-sql-injection-via-searchcustomerphp) covering the flaw in SearchCustomer.php. No specific patches or mitigation guidance is detailed in the available information.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2018-21616
Vulnerability details
Warranty Tracking System 11.06.3 contains an SQL injection vulnerability that allows attackers to execute arbitrary SQL queries by injecting malicious code through the txtCustomerCode, txtCustomerName, and txtPhone POST parameters in SearchCustomer.php. Attackers can submit crafted SQL statements using UNION SELECT…
more
to extract sensitive database information including usernames, database names, and version details.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
SQL injection in public-facing web component (SearchCustomer.php) directly enables remote exploitation of a web application for data access.
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requires validation of POST parameters like txtCustomerCode, txtCustomerName, and txtPhone to block malicious SQL injection payloads before they reach the database.
Mandates identification, reporting, and correction of the SQL injection flaw in SearchCustomer.php to eliminate the vulnerability.
Filters outputs from SQL queries to restrict extraction of sensitive data like usernames, database names, and version details via UNION SELECT.