dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6166

HIGH · 7.3 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in code-projects Vehicle Showroom Management System 1.0. This issue affects some unknown processing of the file /util/UpdateVehicleFunction.php. The manipulation of the argument VEHICLE_ID leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in code-projects Vehicle Showroom Management System 1.0 allows remote attackers to inject malicious SQL queries via the VEHICLE_ID parameter in /util/UpdateVehicleFunction.php. The application fails to properly sanitize user input before using it in SQL queries, enabling attackers to manipulate database operations.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in UpdateVehicleFunction.php to properly sanitize the VEHICLE_ID input. Alternatively, implement input validation and use a web application firewall as a compensating control until the code is remediated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Vehicle Showroom Management System installation
    Search the web server file system for directories containing 'vehicle', 'showroom', or 'Vehicle Showroom Management System'. Check common web root locations such as /var/www/html, /www, /htdocs, or C:\inetpub\wwwroot for the application.
    Affected if The application is present on the server and the version is 1.0 or cannot be determined (treat as vulnerable).
  2. Verify the vulnerable file exists
    Locate the file /util/UpdateVehicleFunction.php within the application directory. Use file system search or check the path directly if the application structure is known.
    Affected if The file /util/UpdateVehicleFunction.php exists in the application root.
  3. Confirm application version
    Check for version indicators such as a version.php file, README.txt, CHANGELOG, or meta tags in index pages. Compare against the affected version 1.0.
    Affected if The installed version is 1.0 or the version cannot be verified (assume vulnerable).
  4. Check network accessibility of the affected endpoint
    Verify that the web application is accessible over HTTP/HTTPS and the /util/UpdateVehicleFunction.php endpoint is reachable. Test with a simple request to confirm the application is live.
    Affected if The application is accessible remotely and the UpdateVehicleFunction.php endpoint responds to requests.
  5. Inspect the vulnerable code pattern
    Examine /util/UpdateVehicleFunction.php for direct use of the VEHICLE_ID parameter in SQL queries without parameterized statements, prepared statements, or input sanitization functions.
    Affected if The code contains unsanitized SQL queries using the VEHICLE_ID parameter from user input.

If Vehicle Showroom Management System 1.0 is installed, the file /util/UpdateVehicleFunction.php exists, and the application is network-accessible, the environment is likely affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries or prepared statements in UpdateVehicleFunction.php to properly sanitize the VEHICLE_ID input. Alternatively, implement input validation and use a web application firewall as a compensating control until the code is remediated.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6166 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data