CVE-2025-8407VulnerabilityPublished 31 Jul 2025

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

Affects code-projects Vehicle ManagementSource CVE Database V5

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
code-projects Vehicle Management	Affected =1.0	Fixed in–

AI-suggested

Organizations should immediately audit their environments to identify any deployments of code-projects Vehicle Management version 1.0. Until an official patch is released, implement strict input validation and sanitization on the 'from' parameter at the web application firewall (WAF) or reverse proxy level to block malicious SQL payloads. Employ network segmentation to isolate the Vehicle Management system from critical internal networks and restrict access to trusted IP addresses only. Monitor logs for unusual database query patterns or repeated requests to /filter2.php with suspicious parameters. Consider deploying runtime application self-protection (RASP) solutions to detect and block injection attempts in real time. If feasible, migrate to a newer, patched version of the software or replace it with an alternative solution. Conduct regular security assessments and penetration testing focused on injection flaws to proactively identify similar vulnerabilities.

Description

A vulnerability, which was classified as critical, has been found in code-projects Vehicle Management 1.0. This issue affects some unknown processing of the file /filter2.php. The manipulation of the argument from leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

Impact

For European organizations using code-projects Vehicle Management 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of vehicle and user data. Exploitation could result in unauthorized disclosure of sensitive information, manipulation of vehicle records, or disruption of fleet management operations. This could impact automotive companies, logistics providers, rental agencies, and public transportation entities relying on this software. The potential for remote exploitation without authentication increases the threat surface, especially for organizations exposing the affected system to external networks or lacking proper network segmentation. Data breaches could lead to regulatory penalties under GDPR, reputational damage, and operational downtime. Additionally, attackers could leverage this vulnerability as a foothold for further lateral movement within corporate networks, amplifying the overall security risk.

Summary

CVE-2025-8407 is a critical SQL Injection vulnerability identified in version 1.0 of the code-projects Vehicle Management software. The vulnerability arises from improper sanitization or validation of the 'from' parameter in the /filter2.php file, allowing an attacker to inject arbitrary SQL commands remotely without requiring authentication or user interaction. This flaw enables an attacker to manipulate backend database queries, potentially leading to unauthorized data access, data modification, or even complete compromise of the database. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a medium severity level, with an attack vector of network (remote exploitation), low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability rated as low to medium. Although no public exploits are currently known in the wild, the disclosure of the vulnerability means attackers could develop exploits. The lack of available patches or mitigations from the vendor increases the risk for users of this software. Given that Vehicle Management systems often handle sensitive vehicle and user data, exploitation could lead to data breaches, operational disruptions, or unauthorized control over vehicle-related information systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Jul 2025, 14:47 UTC

Technical details

References

Community reviews

Related threats