CVE-2018-25161
Received Received - Intake
SQL Injection in Warranty Tracking System Allows Data Extraction

Publication date: 2026-03-06

Last updated on: 2026-03-06

Assigner: VulnCheck

Description
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 to extract sensitive database information including usernames, database names, and version details.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-06
Last Modified
2026-03-06
Generated
2026-06-16
AI Q&A
2026-03-06
EPSS Evaluated
2026-06-14
NVD
CVE-2018-25161
EUVD
EUVD-2018-21616
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
warranty_tracking_system warranty_tracking_system 11.06.3
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The vulnerability is an SQL injection in Warranty Tracking System version 11.06.3. It occurs because the application directly concatenates user input from the POST parameters txtCustomerCode, txtCustomerName, and txtPhone into an SQL query without proper sanitization or parameterization.

This allows an attacker to inject malicious SQL code through these parameters in the SearchCustomer.php script, enabling them to execute arbitrary SQL queries on the database.

For example, attackers can use UNION SELECT statements to extract sensitive information such as usernames, database names, and version details from the backend database.

Impact Analysis

This vulnerability can have serious impacts including unauthorized access to sensitive database information.

  • Attackers can extract confidential data such as usernames and database details.
  • It may lead to data breaches exposing customer information.
  • The integrity of the database could be compromised by executing arbitrary SQL commands.
  • It can undermine the security of the entire application and potentially the underlying system.
Compliance Impact

I don't know

Detection Guidance

[{'type': 'paragraph', 'content': 'This SQL Injection vulnerability can be detected by sending specially crafted POST requests to the SearchCustomer.php endpoint with payloads that include SQL injection attempts in the txtCustomerCode, txtCustomerName, or txtPhone parameters.'}, {'type': 'paragraph', 'content': 'For example, you can use curl commands to test the vulnerability by injecting a UNION SELECT statement to extract database information.'}, {'type': 'list_item', 'content': 'curl -X POST -d "txtCustomerCode=\' UniOn Select CONCAt_WS(0x203a20,USER(),DATABASE(),VERSION()),2,3,4,5,6-- -" http://<target>/Customer/SearchCustomer.php'}, {'type': 'list_item', 'content': 'curl -X POST -d "txtCustomerName=\' UniOn Select CONCAt_WS(0x203a20,USER(),DATABASE(),VERSION()),2,3,4,5,6-- -" http://<target>/Customer/SearchCustomer.php'}, {'type': 'list_item', 'content': 'curl -X POST -d "txtPhone=\' UniOn Select CONCAt_WS(0x203a20,USER(),DATABASE(),VERSION()),2,3,4,5,6-- -" http://<target>/Customer/SearchCustomer.php'}, {'type': 'paragraph', 'content': 'If the server responds with HTTP 200 OK and returns database information, it indicates the presence of the SQL Injection vulnerability.'}] [1]

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2018-25161. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart