Skip to main content
CVE-2025-8409VulnerabilityPublished

CVE-2025-8409: 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 41% 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

Organizations should immediately audit their deployments of code-projects Vehicle Management 1.0 to identify exposed instances of /filter.php. Network-level controls such as web application firewalls (WAFs) should be configured to detect and block SQL injection patterns targeting the 'from' parameter. Input validation and parameterized queries should be implemented as a long-term fix once source code access is possible. Until patches are available, restricting access to the application to trusted internal networks or VPNs can reduce exposure. Regular monitoring of logs for suspicious query strings or error messages related to SQL injection attempts is critical. Organizations should also prepare incident response plans specific to database compromise scenarios. Engaging with the vendor or community to obtain patches or updates is essential. If possible, consider upgrading to newer, unaffected versions or alternative software solutions. Finally, ensure database user permissions follow the principle of least privilege to limit the potential damage from successful injection attacks.

Description

A vulnerability has been found in code-projects Vehicle Management 1.0 and classified as critical. Affected by this vulnerability is an unknown functionality of the file /filter.php. The manipulation of the argument from leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…