CVE-2026-6149
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 · uneditedA flaw has been found in code-projects Vehicle Showroom Management System 1.0. Affected by this issue is some unknown functionality of the file /util/BookVehicleFunction.php. Executing a manipulation of the argument BRANCH_ID can lead to sql injection. The attack may be performed from remote. The exploit has been published 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 confidenceSQL injection vulnerability in Vehicle Showroom Management System 1.0 allows remote attackers to inject malicious SQL queries via the BRANCH_ID parameter in /util/BookVehicleFunction.php. The lack of proper input sanitization or parameterized queries enables attackers to manipulate database queries.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm application installationLocate the Vehicle Showroom Management System web root directory and identify the installed version by checking any version files, about pages, or admin panelsAffected if The application is installed and the version is 1.0 or cannot be determined but the application is present
-
Locate vulnerable fileNavigate to the /util/ directory in the web root and verify that BookVehicleFunction.php existsAffected if The file /util/BookVehicleFunction.php exists in the application directory
-
Inspect BRANCH_ID parameter handlingOpen BookVehicleFunction.php and search for occurrences of 'BRANCH_ID' or 'branch_id' to see how this parameter is processedAffected if The BRANCH_ID parameter is used in SQL queries without proper sanitization, prepared statements, or parameterized queries
-
Check for SQL injection patternsReview the SQL query construction in the file - look for direct string concatenation or interpolation of the BRANCH_ID variable into SQL statementsAffected if The BRANCH_ID parameter is directly concatenated into SQL queries (e.g., 'SELECT ... WHERE BRANCH_ID = ' . $BRANCH_ID) rather than using prepared statements or binding parameters
-
Verify application accessibilityConfirm the /util/BookVehicleFunction.php endpoint is accessible over HTTP/HTTPS to remote attackersAffected if The endpoint is accessible without authentication or with easily bypassable authentication
Your environment is affected if you are running Vehicle Showroom Management System version 1.0 with the file /util/BookVehicleFunction.php present and the BRANCH_ID parameter used in unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dynamic SQL queries with prepared statements/parameterized queries in BookVehicleFunction.php, implement proper input validation for the BRANCH_ID parameter, and apply vendor security patch if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-6149 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6149 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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