Skip to main content
CVE-2025-8373VulnerabilityPublished

CVE-2025-8373: code-projects Vehicle Management · SQL Injection

Affects code-projects Vehicle ManagementSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
code-projects Vehicle ManagementAffected
  • =1.0
Fixed in–

AI-suggested

1. Immediate mitigation should include implementing input validation and parameterized queries or prepared statements in the /print.php script to prevent SQL injection. 2. If source code modification is not immediately feasible, deploying a Web Application Firewall (WAF) with specific rules to detect and block malicious SQL injection payloads targeting the 'sno' parameter can reduce risk. 3. Conduct a thorough code audit of the entire Vehicle Management application to identify and remediate other potential injection points. 4. Monitor application logs for unusual query patterns or repeated failed attempts targeting the 'sno' parameter. 5. Restrict database user privileges to the minimum necessary to limit the impact of any successful injection. 6. Segregate the database server from direct internet exposure and ensure network-level controls limit access to trusted hosts only. 7. Engage with the vendor or community to obtain patches or updates as they become available and apply them promptly. 8. Educate development and operations teams on secure coding practices and the importance of timely vulnerability management.

Description

A vulnerability was found in code-projects Vehicle Management 1.0. It has been classified as critical. This affects an unknown part of the file /print.php. The manipulation of the argument sno leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…