CVE-2025-5652
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 | 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
Can you explain this vulnerability to me?
CVE-2025-5652 is a critical SQL injection vulnerability in the PHPGurukul Complaint Management System 2.0, specifically in the file /admin/between-date-complaintreport.php. The vulnerability occurs because the 'todate' parameter is not properly sanitized or validated before being used in SQL queries. This allows an attacker to inject malicious SQL code remotely, potentially manipulating the database by extracting, modifying, or deleting data without authorization. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data manipulation, and potentially full system compromise. Attackers can exploit it remotely without authentication, threatening the confidentiality, integrity, and availability of the system. This can disrupt business continuity and expose sensitive information. [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" POST parameter in the /admin/between-date-complaintreport.php endpoint for SQL injection. Commands using tools like sqlmap can be used to automate detection, for example: sqlmap -u "http://target/cms/admin/between-date-complaintreport.php" --data="todate=2025-01-01" -p todate. Manual testing can include sending crafted POST requests with payloads such as "todate=2025-01-01' AND 6688=6688--" to check for boolean-based blind SQL injection, or "todate=2025-01-01' AND (SELECT SLEEP(5))--" for time-based blind SQL injection. Additionally, Google Dorking with queries like inurl:admin/between-date-complaintreport.php can help identify vulnerable targets. [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 "todate" and "fromdate" parameters to ensure they conform to expected formats, and limiting database user permissions to the minimum necessary to reduce potential damage. Avoid using high-privilege database accounts for routine operations. Since no known countermeasures are currently available, replacing the affected component with an alternative product is also suggested. [2, 3]