CVE-2025-5653
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | complaint_management_system | 2.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
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/between-date-userreport.php endpoint for SQL injection via the 'todate' and 'fromdate' parameters. You can use tools like sqlmap to automate detection and exploitation. Example sqlmap command: sqlmap -u "http://target/admin/between-date-userreport.php" --data="fromdate=2000-01-01&todate=2025-01-01" --risk=3 --level=5 --batch. Additionally, Google Dorking with the query inurl:admin/between-date-userreport.php can help identify vulnerable targets on the network. [2, 3]
Can you explain this vulnerability to me?
CVE-2025-5653 is a critical SQL injection vulnerability in the PHPGurukul Complaint Management System 2.0, specifically in the /admin/between-date-userreport.php file. The vulnerability occurs because the 'todate' and 'fromdate' parameters are not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, manipulating the database queries to perform unauthorized actions such as extracting, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to the database, allowing attackers to leak sensitive information, modify or delete records, take control of the system, and disrupt service availability. This poses severe security and operational risks including data breaches and loss of system integrity. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'fromdate' and 'todate' parameters to ensure they conform to expected date formats, and restricting database user permissions to the minimum necessary to limit potential damage. Since no known countermeasures or patches are available, it is recommended to replace the affected component with an alternative product if possible. [2, 3]