CVE-2025-5913
BaseFortify
Publication date: 2025-06-10
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| anujk305 | vehicle_record_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-5913 is a critical SQL injection vulnerability in the PHPGurukul Vehicle Record Management System version 1.0, specifically in the /admin/search-vehicle.php file. The vulnerability arises because the "searchinputdata" parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially manipulating database queries to access, modify, or delete sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, leakage of sensitive information, modification or deletion of records, full system control takeover, and disruption of services. Since exploitation requires no authentication and is easy to perform, attackers can remotely compromise the system, threatening confidentiality, integrity, and availability of the data and services. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter 'searchinputdata' in the /admin/search-vehicle.php endpoint for SQL injection. You can use tools like sqlmap with advanced options to automate detection. Example sqlmap command: sqlmap -u "http://<target>/vehiclerecordsystem/admin/search-vehicle.php" --data="searchinputdata=test" --batch --threads=10 --level=5 --risk=3 --random-agent --tamper=space2comment --technique=BEUST. Additionally, Google dorking with the query inurl:admin/search-vehicle.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'searchinputdata' parameter to ensure only expected input formats are accepted. 3) Minimize database user permissions by avoiding elevated privileges for the database user used by the application. If possible, replace the affected component with an alternative product as no known countermeasures are documented. [2, 3]