CVE-2025-8375VulnerabilityPublished 31 Jul 2025

CVE-2025-8375: 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.5% chance of exploitation in 30 days – higher than 48% 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

1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block suspicious SQL injection payloads targeting the /addvehicle.php endpoint, particularly focusing on the 'vehicle' parameter. 2. Conduct a thorough code review and apply input validation and parameterized queries or prepared statements to sanitize and safely handle all user inputs in the affected endpoint. 3. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. 4. Monitor logs for unusual database queries or errors indicative of injection attempts. 5. If possible, isolate the Vehicle Management system within a segmented network zone to reduce lateral movement risk. 6. Engage with the vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 7. Educate developers and administrators on secure coding practices to prevent similar vulnerabilities in future releases.

Description

A vulnerability was found in code-projects Vehicle Management 1.0. It has been rated as critical. This issue affects some unknown processing of the file /addvehicle.php. The manipulation of the argument vehicle 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-related data. Compromise of the database could lead to exposure of sensitive information such as vehicle registration details, user data, or operational records. This could result in regulatory non-compliance, especially under GDPR, leading to legal and financial penalties. Additionally, data manipulation could disrupt business operations, causing availability issues or erroneous vehicle management decisions. The remote and unauthenticated nature of the exploit increases the risk of automated attacks or mass scanning campaigns targeting vulnerable installations. Organizations in sectors such as automotive services, fleet management, or government agencies managing vehicle data are particularly at risk. The lack of known exploits in the wild currently reduces immediate threat but does not eliminate the risk of future exploitation.

Summary

CVE-2025-8375 is a SQL Injection vulnerability identified in version 1.0 of the code-projects Vehicle Management software. The vulnerability arises from improper handling of the 'vehicle' parameter in the /addvehicle.php endpoint, allowing an attacker to inject malicious SQL code. This flaw can be exploited remotely without any authentication or user interaction, as the vulnerable parameter is directly manipulable via HTTP requests. The injection can lead to unauthorized access to the backend database, enabling attackers to read, modify, or delete sensitive data stored within the Vehicle Management system. Given the nature of SQL Injection, the attacker could potentially escalate the impact to compromise the entire database server or pivot to other parts of the network. The CVSS 4.0 score is 6.9 (medium severity), reflecting that while the attack vector is network-based and requires no privileges or user interaction, the impact on confidentiality, integrity, and availability is limited to low to moderate levels. The vulnerability is publicly disclosed, but no known exploits are currently observed in the wild. No patches or fixes have been linked yet, indicating that affected organizations must rely on mitigation strategies until an official update is available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Jul 2025, 09:32 UTC

Technical details

References

Community reviews

Related threats