CVE-2025-7489
BaseFortify
Publication date: 2025-07-12
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 |
|---|---|---|
| phpgurukul | vehicle_parking_management_system | 1.13 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-7489 is a critical SQL injection vulnerability in PHPGurukul Vehicle Parking Management System version 1.13. It exists in the /admin/search-vehicle.php file, specifically through the 'searchdata' parameter. This parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This can lead to unauthorized manipulation of SQL queries and unauthorized access to the database. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to gain unauthorized access to the database, leak sensitive data, manipulate or delete data, gain full system control, and cause service disruptions. The attack can be performed remotely without authentication, making it highly accessible and dangerous. [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 "searchdata" parameter in the /admin/search-vehicle.php file for SQL injection. Tools like sqlmap can be used to automate detection by targeting the "searchdata" POST parameter. A proof-of-concept payload includes time-based blind SQL injection such as injecting `111' AND (SELECT SLEEP(5))--` to observe delays. Additionally, manual testing can involve sending crafted HTTP POST requests with malicious payloads in the "searchdata" parameter to check for SQL injection behavior. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing strict input validation and filtering to ensure inputs conform to expected formats, and minimizing database user permissions by avoiding elevated privilege accounts for routine operations. Since no known countermeasures or patches are documented, replacing the affected product with an alternative solution is also suggested. [2, 3]