Is there a public PoC exploit available for CVE-2026-6037?

Yes, a public proof-of-concept exploit is available for CVE-2026-6037. Prioritise patching immediately. EPSS: 0.0%.

Vehicle Showroom Management System CVE-2026-6037

Q: What is the CVSS score of CVE-2026-6037?

CVE-2026-6037 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-21350 MEDIUM

SQL Injection (CWE-89)

2026-04-10 VulDB

GHSA-734f-8p5w-pjw7

PHP SQLi Vehicle Showroom Management System Code Projects

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.3 HIGH

Network-exposed endpoint requires no authentication (PR:N); unsanitized SQL parameter yields partial database read/write (C:L/I:L) and minor availability risk from destructive queries (A:L).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jul 24, 2026 - 08:10 vuln.today

CVSS changed

Apr 29, 2026 - 01:11 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

PoC Detected

Apr 10, 2026 - 09:16 vuln.today

Public exploit code

EUVD ID Assigned

Apr 10, 2026 - 08:45 euvd

EUVD-2026-21350

CVE Published

Apr 10, 2026 - 08:30 cve.org

MEDIUM 5.5

CVE Published

Apr 10, 2026 - 08:30 nvd

MEDIUM 6.9

DescriptionCVE.org

A vulnerability was determined in code-projects Vehicle Showroom Management System 1.0. This affects an unknown function of the file /util/AddVehicleFunction.php. This manipulation of the argument BRANCH_ID causes sql injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.

AnalysisAI

SQL injection in code-projects Vehicle Showroom Management System 1.0 exposes the /util/AddVehicleFunction.php endpoint to remote unauthenticated database manipulation via the unsanitized BRANCH_ID parameter. The CVSS 4.0 vector confirms no authentication or user interaction is required, and a public proof-of-concept exploit is available on GitHub. EPSS sits at 0.03% (9th percentile), indicating minimal observed in-the-wild exploitation despite the POC's existence, consistent with this product's extremely narrow deployment footprint.

Technical ContextAI

The vulnerable component is a PHP-based vehicle data management endpoint (/util/AddVehicleFunction.php) within code-projects' Vehicle Showroom Management System 1.0 - a niche open-source PHP web application. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): the BRANCH_ID HTTP parameter is concatenated directly into a SQL query without parameterization or prepared statements, a textbook Type 1 (in-band) SQL injection pattern. The CPE identifier cpe:2.3:a:code-projects:vehicle_showroom_management_system:*:*:*:*:*:*:*:* uses a wildcard version field, though EUVD specifically confirms version 1.0 as the affected release. No database type is specified in the available data, but typical code-projects PHP applications use MySQL.

RemediationAI

No vendor-released patch has been identified at the time of analysis - patch status is unconfirmed and no fix version has been published by code-projects. The most effective immediate control is to restrict network access to /util/AddVehicleFunction.php at the web server layer (e.g., deny all external IPs via Apache .htaccess or nginx location block); this eliminates remote exploitability with no application-side trade-off if the endpoint is only needed internally. As a secondary compensating control, deploy a WAF rule to reject requests containing SQL metacharacters in the BRANCH_ID parameter - note this may require tuning to avoid false positives on legitimate branch identifiers. For a permanent fix, the application code must be refactored to use PDO prepared statements or MySQLi parameterized queries for all SQL operations involving user-supplied input. The POC exploit is documented at https://github.com/TAnNbR/CVE/issues/4 and VulDB tracking is at https://vuldb.com/vuln/356618.