CVE-2025-7490
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-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-7490 is a critical SQL injection vulnerability in PHPGurukul Vehicle Parking Management System version 1.13. It exists in the /admin/reg-users.php file through the 'del' parameter, which is used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, manipulating SQL queries to perform unauthorized database operations such as data leakage, tampering, or full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. Attackers can remotely execute arbitrary SQL commands, impacting the confidentiality, integrity, and availability of the system. The vulnerability is easy to exploit and a proof-of-concept is publicly available. [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 'del' parameter in the /admin/reg-users.php file for SQL injection. A time-based blind SQL injection payload such as `del=3' RLIKE SLEEP(5)--` can be used to confirm the injection point by causing a delay in the database response. Additionally, tools like sqlmap can be used to automate detection and enumeration of the vulnerability. An example vulnerable request is a GET request to `/vpms/admin/reg-users.php?del=3`. You can also identify potentially vulnerable targets using Google dorking with queries like `inurl:admin/reg-users.php`. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats and block malicious data. 3) Limiting database user permissions to the minimum necessary, avoiding high-privilege accounts such as 'root' or 'admin' for routine operations. If possible, replace the affected component with an alternative product as no known mitigations or countermeasures have been reported. [2, 3]