# CVE-2026-6148: code-projects Vehicle Showroom Management System MonthTotalReportUpdateFunction.php sql injection

> Remote attackers can exploit SQL injection in the BRANCH_ID parameter to read or modify database contents in the Vehicle Showroom Management System.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-v36w-f92j-7386

## What is CVE-2026-6148?

CVE-2026-6148 is a medium-severity SQL injection vulnerability in code-projects Vehicle Showroom Management System, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-6148?


## How do I fix CVE-2026-6148?

No fix has been published for CVE-2026-6148 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6148 being exploited?

There is no known exploitation of CVE-2026-6148 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6148 and fix it if it is affected.

What it is: CVE-2026-6148 is a medium-severity SQL injection vulnerability in code-projects Vehicle Showroom Management System, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6148 in the wild and no public exploit code.

Affected product: code-projects Vehicle Showroom Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6148/ (Markdown: https://insights.sbomify.com/CVE-2026-6148/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6148
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6148
- OSV: https://osv.dev/vulnerability/CVE-2026-6148

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6148/
Summaries are generated and may contain mistakes; the official description above is the record.