CVE-2026-6165

7.3

code-projects · Vehicle Showroom Management System

A SQL injection vulnerability exists in the Vehicle Showroom Management System 1.0, specifically within the /util/Login_check.php file, allowing remote attackers to manipulate the ID argument.

Executive summary

A critical SQL injection vulnerability in the code-projects Vehicle Showroom Management System allows unauthenticated remote attackers to compromise the application database.

Vulnerability

This is a SQL injection flaw (CWE-89) triggered by improper input validation of the ID parameter within the /util/Login_check.php file. The vulnerability is exploitable by unauthenticated remote attackers.

Business impact

The ability to perform remote SQL injection poses a significant risk to the confidentiality, integrity, and availability of the application. An attacker could potentially extract sensitive user data, bypass authentication mechanisms, or modify database records, leading to unauthorized access and potential system compromise. With a CVSS score of 7.3, this high-severity flaw requires immediate attention to prevent unauthorized data exfiltration.

Remediation

Immediate Action: Since no official patch is currently available, administrators should restrict access to the affected web directory or disable the vulnerable Vehicle Showroom Management System until a secure update is released.

Proactive Monitoring: Review web server access logs for anomalous requests containing SQL syntax patterns targeted at the /util/Login_check.php endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection payloads targeting the identified parameter.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists as documented in the referenced GitHub issue.

Analyst recommendation

Given the availability of a public proof-of-concept and the ease of remote exploitation, this vulnerability presents a clear and present danger to affected environments. Organizations must prioritize the implementation of compensating controls, such as WAF filtering, to mitigate the risk while awaiting a vendor-supplied patch. Failure to address this flaw could lead to a full database compromise.

More code-projects CVEs

Sources

Originally found and disclosed by Minji (VulDB User), per the CVE Program record.