dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6148

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 vulnerability was detected in code-projects Vehicle Showroom Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /util/MonthTotalReportUpdateFunction.php. Performing a manipulation of the argument BRANCH_ID results in sql injection. The attack is possible to be carried out remotely. The exploit is now public 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 · moderate confidence

SQL injection vulnerability in code-projects Vehicle Showroom Management System 1.0 allows remote attackers to inject malicious SQL queries through the BRANCH_ID parameter in /util/MonthTotalReportUpdateFunction.php.

MitigationReplace dynamic SQL queries with parameterized queries (prepared statements) for the BRANCH_ID parameter and all user inputs. Apply input validation and sanitize all database inputs. Apply vendor patches if available.

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 for the file MonthTotalReportUpdateFunction.php in the web root directory, typically under /util/ folder
    Affected if The file /util/MonthTotalReportUpdateFunction.php exists on the server and is accessible via web
  2. Identify the application and version
    Inspect the application for its name and version. Check index files, README, or admin panels for 'Vehicle Showroom Management System' version 1.0
    Affected if The application is code-projects Vehicle Showroom Management System version 1.0
  3. Verify the BRANCH_ID parameter usage
    Examine the source code of MonthTotalReportUpdateFunction.php and search for direct use of $_GET or $_POST['BRANCH_ID'] in SQL queries without prepared statements
    Affected if The code contains SQL queries that incorporate the BRANCH_ID parameter directly without parameterization
  4. Confirm database interaction
    Check if the application database is MySQL/MariaDB and if the affected PHP file connects to it
    Affected if The application uses a database and the vulnerable file processes SQL queries with user input
  5. Assess network exposure
    Determine if the /util/MonthTotalReportUpdateFunction.php endpoint is reachable from the network
    Affected if The vulnerable endpoint is exposed to network users without authentication

The environment is affected if the Vehicle Showroom Management System version 1.0 is installed and the /util/MonthTotalReportUpdateFunction.php file processes the BRANCH_ID parameter directly in SQL queries.

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) for the BRANCH_ID parameter and all user inputs. Apply input validation and sanitize all database inputs. Apply vendor patches if available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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