Home/CVE/A vulnerability was found in code-projects Vehicle Showroom Management System 1.0. This vulnerability affects unknown co
CVE
CVE-2026-6151
A vulnerability was found in code-projects Vehicle Showroom Management System 1.0. This vulnerability affects unknown co
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.
HIGH · CVSS 7.3
EPSS 0.00043
EPSS exploitation odds0.04% · top 86%
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-6151, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
0.04%
Top 86%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
poc
Automatable
yes
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LLifecycle
- 13 Apr 2026Published to NVD
- 29 Apr 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-10 · Buffer Overflow via Environment Variables CAPEC-CAPEC-101 · Server Side Include (SSI) Injection CAPEC-CAPEC-105 · HTTP Request Splitting CAPEC-CAPEC-108 · Command Line Execution through SQL Injection CAPEC-CAPEC-109 · Object Relational Mapping Injection CAPEC-CAPEC-110 · SQL Injection through SOAP Parameter Tampering CAPEC-CAPEC-120 · Double Encoding CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-135 · Format String Injection CAPEC-CAPEC-14 · Client-side Injection-induced Buffer Overflow CAPEC-CAPEC-24 · Filter Failure through Buffer Overflow CAPEC-CAPEC-250 · XML Injection
⬡
Weakness Classification
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2004-2570
Opera before 7.54 allows remote attackers to modify properties and methods of th...
same CWE-74
CVE-2004-1157
Opera 7.x up to 7.54, and possibly other versions, allows remote attackers to sp...
same CWE-74
CVE-2005-3007
Opera before 8.50 allows remote attackers to spoof the content type of files via...
same CWE-74
CVE-2005-3750
Opera before 8.51 on Linux and Unix systems allows remote attackers to execute a...
same CWE-74
CVE-2002-0999
Multiple SQL injection vulnerabilities in CARE 2002 before beta 1.0.02 allow rem...
same CWE-89
CVE-2002-2252
SQL injection vulnerability in auth.inc.php in Thatware 0.5.0 and earlier allows...
same CWE-89
CVE-2002-2277
SQL injection vulnerability in mod_search/index.php in PortailPHP 0.99 allows re...
same CWE-89
CVE-2002-2304
SQL injection vulnerability in admin/auth/checksession.php in MyPHPLinks 2.1.9 a...
same CWE-89
🔗
References & Sources
5Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.