Skip to main content

CVE-2025-5913: SQL Injection in PHPGurukul Vehicle Record Management System

Medium
VulnerabilityCVE-2025-5913cvecve-2025-5913
Published: Tue Jun 10 2025 (06/10/2025, 03:31:06 UTC)
Source: CVE Database V5
Vendor/Project: PHPGurukul
Product: Vehicle Record Management System

Description

A vulnerability was found in PHPGurukul Vehicle Record Management System 1.0. It has been rated as critical. This issue affects some unknown processing of the file /admin/search-vehicle.php. The manipulation of the argument searchinputdata leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.

AI-Powered Analysis

AILast updated: 07/11/2025, 02:16:55 UTC

Technical Analysis

CVE-2025-5913 is a critical SQL Injection vulnerability identified in version 1.0 of the PHPGurukul Vehicle Record Management System. The vulnerability arises from improper sanitization and validation of the 'searchinputdata' parameter in the /admin/search-vehicle.php file. An attacker can remotely exploit this flaw by injecting malicious SQL code through this parameter, which is processed by the backend database without adequate filtering or parameterization. This allows unauthorized manipulation of SQL queries, potentially leading to unauthorized data access, data modification, or even complete compromise of the underlying database. The vulnerability does not require any authentication or user interaction, making it exploitable by any remote attacker with network access to the affected system. The CVSS 4.0 base score is 6.9, indicating a medium severity level, with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N). The impact on confidentiality, integrity, and availability is limited but present (VC:L, VI:L, VA:L), meaning partial compromise of data and system functionality is possible. Although no known exploits are currently reported in the wild, the public disclosure of the exploit code increases the risk of exploitation. The vulnerability affects only version 1.0 of the PHPGurukul Vehicle Record Management System, which is a specialized software used for managing vehicle records, likely deployed in administrative or governmental environments.

Potential Impact

For European organizations, especially those in the public sector or private companies managing vehicle fleets or transportation logistics, this vulnerability poses a significant risk. Exploitation could lead to unauthorized access to sensitive vehicle records, including registration details, owner information, and possibly financial data. This could result in data breaches violating GDPR regulations, leading to legal and financial penalties. Additionally, attackers could manipulate or delete vehicle records, disrupting operational processes and causing reputational damage. Since the vulnerability allows remote exploitation without authentication, attackers could leverage it as an entry point for further lateral movement within the network. The impact is particularly critical for organizations relying on this specific software version without timely patching or mitigation, as the integrity and availability of vehicle management systems are crucial for regulatory compliance and operational continuity.

Mitigation Recommendations

Organizations using PHPGurukul Vehicle Record Management System version 1.0 should immediately implement the following mitigations: 1) Apply vendor patches or updates once available; if no patch exists, consider upgrading to a newer, secure version of the software. 2) Implement Web Application Firewall (WAF) rules to detect and block SQL injection patterns targeting the 'searchinputdata' parameter. 3) Restrict network access to the administrative interface (/admin/search-vehicle.php) by IP whitelisting or VPN access to reduce exposure. 4) Conduct thorough input validation and parameterized queries in the application code to prevent injection attacks. 5) Monitor logs for suspicious queries or repeated failed attempts targeting the vulnerable endpoint. 6) Perform regular security assessments and penetration testing focusing on injection vulnerabilities. 7) Educate system administrators and developers about secure coding practices and the risks of SQL injection. These steps go beyond generic advice by focusing on immediate protective controls and long-term secure development practices specific to this vulnerability and affected component.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-06-09T08:09:28.615Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68487f591b0bd07c3938aa4d

Added to database: 6/10/2025, 6:54:17 PM

Last enriched: 7/11/2025, 2:16:55 AM

Last updated: 8/5/2025, 10:41:52 AM

Views: 15

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats