PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-6165 code-projects CVE debrief

A weakness has been identified in code-projects Vehicle Showroom Management System 1.0. This vulnerability affects unknown code of the file /util/Login_check.php. Executing a manipulation of the argument ID can lead to sql injection. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks.

Vendor
code-projects
Product
Vehicle Showroom Management System
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-13
Original CVE updated
2026-10-26
Advisory published
2026-04-13
Advisory updated
2026-10-26

Who should care

Defenders responsible for Vehicle Showroom Management System 1.0 deployments should assess exposure and prioritize verification and mitigation. Defenders should care about CVE-2026-6165 because it is a SQL injection vulnerability in code-projects Vehicle Showroom Management System 1.0 that can be exploited remotely. The scope of affected systems and versions requires verification.

Why it matters

Defenders should care about CVE-2026-6165 because it is a SQL injection vulnerability in code-projects Vehicle Showroom Management System 1.0 that can be exploited remotely. The scope of affected systems and versions requires verification.

  • Verify potential SQL injection attacks
  • Assess exposure of Vehicle Showroom Management System 1.0 deployments
  • Prioritize patching or mitigation efforts

Technical summary

The vulnerability is a SQL injection weakness in the /util/Login_check.php file of code-projects Vehicle Showroom Management System 1.0. The attack can be launched remotely by manipulating the ID argument. This weakness affects unknown code and has been made publicly available for exploitation. Defenders should prioritize verifying the presence of this vulnerability in their systems and applying patches or mitigations as available. The CVE record was published on 2026-04-13T06:16:07.373Z and has not been modified since then.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their systems and applying patches or mitigations as available.

Recommended defensive actions

  • Verify the presence of this vulnerability in Vehicle Showroom Management System 1.0
  • Apply patches or mitigations as available
  • Monitor for potential SQL injection attacks
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in code-projects Vehicle Showroom Management System 1.0. The scope of affected systems and versions requires verification. Defenders should verify potential SQL injection attacks and assess exposure of Vehicle Showroom Management System 1.0 deployments. The exploit has been made available to the public and could be used for attacks. Limited source detail is available, so explicit evidence-limit language and defensive verification tasks are necessary.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-6165 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-6165

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-6165 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-6165

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.