CVE-2018-25192
SQL Injection in GPS Tracking System 2.12 Enables Unauthorized Access
Publication date: 2026-03-06
Last updated on: 2026-03-06
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2018-25192 is an SQL injection vulnerability found in GPS Tracking System version 2.12 and earlier. It occurs in the username parameter of the login.php endpoint. An attacker can send specially crafted POST requests with malicious SQL code in the username field to bypass authentication.
This means that without valid credentials, an attacker can manipulate the SQL query executed by the application to gain unauthorized access to the system.
How can this vulnerability impact me? :
This vulnerability allows unauthenticated attackers to bypass the login process and gain unauthorized access to the GPS Tracking System.
Such unauthorized access can lead to exposure or manipulation of sensitive tracking data, compromise of user accounts, and potential further exploitation of the system.
Because the vulnerability has a high severity score (CVSS v4.0 score of 8.8), it represents a significant security risk if left unpatched.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by sending crafted POST requests to the login.php endpoint with SQL injection payloads in the username parameter and observing if authentication is bypassed.'}, {'type': 'paragraph', 'content': 'For example, you can use the following curl command to test for the vulnerability:'}, {'type': 'list_item', 'content': 'curl -X POST -d "username=\'or 1=1 or \'\'=\'&password=" http://target/login.php -v'}, {'type': 'paragraph', 'content': 'If the response results in a successful login redirect (HTTP 302 Found) to index.php without valid credentials, the system is vulnerable.'}] [2]
What immediate steps should I take to mitigate this vulnerability?
I don't know