dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6037

HIGH · 7.3 CVSS v3.1 Published 2026-04-10
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 vulnerability was determined in code-projects Vehicle Showroom Management System 1.0. This affects an unknown function of the file /util/AddVehicleFunction.php. This manipulation of the argument BRANCH_ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

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 Vehicle Showroom Management System 1.0's /util/AddVehicleFunction.php file. The BRANCH_ID parameter is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL code.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements. Validate and sanitize all user inputs, especially the BRANCH_ID parameter. Apply input validation and output encoding as defense-in-depth measures.

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. Locate the affected PHP file
    Search the web root directory for the file /util/AddVehicleFunction.php. Use a command like 'find /var/www -path "*/util/AddVehicleFunction.php" 2>/dev/null' or check the application's file structure.
    Affected if The file exists in the application directory, indicating the vulnerable component is present.
  2. Confirm the application version
    Check for version indicators in the application - look for a version file, changelog, or admin panel that displays the software version. Common locations include /includes/config.php, /about.php, or a README file in the web root.
    Affected if The installed version is Vehicle Showroom Management System 1.0.
  3. Verify the BRANCH_ID parameter is handled by the application
    Examine the /util/AddVehicleFunction.php file to confirm it processes the BRANCH_ID parameter in a POST or GET request. Search for '$_POST["BRANCH_ID"]' or '$_GET["BRANCH_ID"]' within the file.
    Affected if The file contains code that retrieves the BRANCH_ID parameter from user input without visible sanitization.
  4. Check if the vulnerable endpoint is exposed
    Test if the AddVehicleFunction.php endpoint is accessible. Attempt a HEAD or GET request to /util/AddVehicleFunction.php on the web server to confirm it responds.
    Affected if The endpoint is accessible and responds to requests, meaning the attack surface is exposed.
  5. Inspect the SQL query implementation
    Open /util/AddVehicleFunction.php and locate the database query that uses BRANCH_ID. Look for direct string concatenation or lack of prepared statements in the query handling.
    Affected if The BRANCH_ID parameter is used directly in SQL queries without parameterized queries, prepared statements, or evident input sanitization functions.

The environment is affected if Vehicle Showroom Management System 1.0 is installed, the file /util/AddVehicleFunction.php exists, and the BRANCH_ID parameter is used in unsanitized SQL queries accessible via the web.

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/prepared statements. Validate and sanitize all user inputs, especially the BRANCH_ID parameter. Apply input validation and output encoding as defense-in-depth measures.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6037 — 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-6037 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