CVE-2018-25167
SQL Injection in Net-Billetterie 2.9 Login Allows Data Theft
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
| Vendor | Product | Version / Range |
|---|---|---|
| net-billetterie | net-billetterie | 2.9 |
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
How can this vulnerability impact me? :
This vulnerability allows attackers to execute arbitrary SQL queries on the database without authentication. As a result, attackers can bypass login authentication, gaining unauthorized access to the system.
Additionally, attackers can extract sensitive information such as usernames, passwords, and system credentials from the database, potentially leading to further compromise of the system and data breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "The vulnerability in Net-Billetterie 2.9 is an SQL injection flaw located in the login parameter of the login.inc.php script. It occurs because user input from the 'login' POST parameter is directly embedded into an SQL query without proper sanitization or parameterization. This allows unauthenticated attackers to inject arbitrary SQL code."}, {'type': 'paragraph', 'content': "Specifically, the application constructs an SQL query using the 'login' and 'pass' POST parameters, hashing the password with MD5, but fails to sanitize the 'login' input. This enables attackers to manipulate the SQL query to bypass authentication or extract sensitive information from the database."}] [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This SQL injection vulnerability can be detected by testing the 'login' POST parameter of the login.inc.php script for unsanitized input handling."}, {'type': 'paragraph', 'content': "One way to detect it is by sending specially crafted SQL injection payloads in the 'login' parameter and observing if the application returns database errors or unexpected data."}, {'type': 'paragraph', 'content': 'For example, you can use curl to send a POST request with an injection payload like:'}, {'type': 'list_item', 'content': 'curl -X POST -d "login=\' OR \'1\'=\'1" -d "pass=anything" http://target-site/login.inc.php'}, {'type': 'paragraph', 'content': 'If the response indicates successful login or reveals database information, the vulnerability is present.'}, {'type': 'paragraph', 'content': 'Additionally, automated SQL injection detection tools such as sqlmap can be used to test the login parameter:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://target-site/login.inc.php" --data="login=admin&pass=admin" -p login --batch'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': "Immediate mitigation steps include sanitizing and parameterizing all user inputs, especially the 'login' POST parameter in login.inc.php."}, {'type': 'paragraph', 'content': 'Specifically, avoid directly embedding user input into SQL queries. Use prepared statements or parameterized queries instead of deprecated mysql_query functions.'}, {'type': 'paragraph', 'content': 'Additionally, consider updating or patching the application to a version that fixes this vulnerability if available.'}, {'type': 'paragraph', 'content': 'As a temporary measure, restrict access to the login page or implement Web Application Firewall (WAF) rules to block common SQL injection payloads.'}] [1]