CVE-2025-7522
BaseFortify
Publication date: 2025-07-13
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-7522 is a critical SQL injection vulnerability in PHPGurukul Vehicle Parking Management System version 1.13, specifically in the file /admin/bwdates-reports-details.php. The vulnerability arises because the 'fromdate' and 'todate' parameters are used directly in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, manipulating SQL commands to perform unauthorized database operations such as data leakage, data manipulation, or system control takeover. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized access to the database, allowing attackers to leak sensitive data, manipulate or delete data, disrupt services, or potentially take control of the affected system. Since the attack can be launched remotely without authentication, it poses a significant risk to the confidentiality, integrity, and availability of the system and its data. [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 'todate' parameter in the /admin/bwdates-reports-details.php file for SQL injection. Tools like sqlmap can be used to automate detection targeting the 'todate' parameter. Example sqlmap command: sqlmap -u "http://target/admin/bwdates-reports-details.php?todate=2025-07-01" --risk=3 --level=5 --dbs. Additionally, manual testing with payloads such as boolean-based blind injection ('2025-07-01' AND 8329=8329--), time-based blind injection ('2025-07-01' AND (SELECT SLEEP(5))--), or UNION-based injection can be performed to confirm the vulnerability. Google dorking with the query inurl:admin/bwdates-reports-details.php can help identify potentially 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 separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering on the 'fromdate' and 'todate' parameters to ensure they conform to expected date formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. Since no known countermeasures or patches are documented, replacing the affected component with an alternative product is also suggested to ensure security. [2, 3]