CVE-2025-5654
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
Can you explain this vulnerability to me?
CVE-2025-5654 is a critical SQL injection vulnerability in the PHPGurukul Complaint Management System version 2.0. It exists in the /admin/edit-state.php file where the 'description' parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code remotely, potentially manipulating the database to perform unauthorized actions such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to gain unauthorized access to your database, leading to data leakage, data manipulation, and potentially full system control. It can compromise the confidentiality, integrity, and availability of your system, causing service disruption and loss of trust. [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 "description" parameter in the /admin/edit-state.php file for SQL injection. A proof-of-concept time-based blind SQL injection payload is: state=Delhi&description=Delhi-DL' RLIKE SLEEP(5)-- WjXY&submit=. Using tools like sqlmap can automate detection and enumeration of databases via this parameter. Additionally, Google Dorking with queries such as "inurl:admin/edit-state.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 "description" parameter, and minimizing database user privileges by avoiding high-privilege accounts for routine operations. Since no known countermeasures or patches are available, replacing the affected component with an alternative product is recommended. [2, 3]