dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6151

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 found in code-projects Vehicle Showroom Management System 1.0. This vulnerability affects unknown code of the file /util/PaymentStatusFunction.php. The manipulation of the argument CUSTOMER_ID results in sql injection. It is possible to launch the attack remotely. The exploit has been made public and could 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 the /util/PaymentStatusFunction.php file of the Vehicle Showroom Management System 1.0. The CUSTOMER_ID parameter is not properly sanitized before being used in SQL queries, allowing remote attackers to inject malicious SQL code.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements. Validate and sanitize all user inputs before using them in database operations.

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. Confirm Vehicle Showroom Management System installation
    Locate the web application root directory and identify if it is the Vehicle Showroom Management System by checking for characteristic files such as index.php, admin/, or login pages specific to this system
    Affected if The system is not the Vehicle Showroom Management System, then this CVE does not apply
  2. Verify the application version is 1.0
    Check the application version by looking for a version file, About page, or checking the source code for a version constant. Common locations include a config file, footer of admin pages, or a readme.txt file
    Affected if The installed version is not 1.0, then it may not be affected (unless other versions contain the same vulnerable code)
  3. Locate the vulnerable file PaymentStatusFunction.php
    Navigate to the /util/ directory under the web application root and confirm the presence of PaymentStatusFunction.php. Use a file search or check the directory listing
    Affected if The file /util/PaymentStatusFunction.php does not exist, then this specific CVE does not apply
  4. Inspect CUSTOMER_ID parameter handling in the vulnerable file
    Open /util/PaymentStatusFunction.php and search for occurrences of CUSTOMER_ID. Examine how this parameter is used in SQL queries - look for direct concatenation or lack of parameterization
    Affected if The CUSTOMER_ID parameter is used in SQL queries without proper sanitization, prepared statements, or parameterized queries, then the system is vulnerable
  5. Confirm the payment status function is accessible
    Determine if the PaymentStatusFunction.php is accessible via the web by checking if it is directly callable or if there are routes/endpoints that invoke it with user-controlled CUSTOMER_ID input
    Affected if The function handling CUSTOMER_ID is exposed to user input and processes SQL queries without sanitization, the system is vulnerable to SQL injection

The system is affected if it runs Vehicle Showroom Management System version 1.0, contains the /util/PaymentStatusFunction.php file, and processes the CUSTOMER_ID parameter in SQL queries without sanitization or prepared statements.

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. Validate and sanitize all user inputs before using them in database operations.

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-6151 — 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-6151 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