CVE-2025-5663
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-06
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | auto\/taxi_stand_management_system | 1.0 |
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-5663 is a critical SQL injection vulnerability in PHPGurukul Auto Taxi Stand Management System version 1.0, specifically in the /admin/search-autoortaxi.php file. The vulnerability arises because the 'searchdata' parameter is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This enables unauthorized execution of arbitrary SQL commands remotely without authentication, potentially leading to unauthorized database access, data leakage, modification, or deletion. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data tampering, deletion of data, full system compromise, and potential service disruption. Attackers can exploit it remotely without authentication, using techniques like time-based blind SQL injection or UNION queries to extract or manipulate data. This compromises the confidentiality, integrity, and availability of the affected system. [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' POST parameter in the /admin/search-autoortaxi.php file for SQL injection. One effective method is using the sqlmap tool to automate SQL injection detection. Example command: sqlmap -u "http://targetsite/admin/search-autoortaxi.php" --data="searchdata=111" --risk=3 --level=5 --batch. Additionally, time-based blind SQL injection can be tested by injecting payloads such as: searchdata=111' AND (SELECT SLEEP(5))-- - to observe response delays. [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) Apply strict input validation and filtering on the 'searchdata' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary, avoiding high-privilege accounts for routine operations. 4) If possible, replace the affected component with an alternative product as no known countermeasures currently exist. These steps help protect system security and data integrity. [2, 3]