CVE-2025-5655
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-5655 is a critical SQL injection vulnerability in the PHPGurukul Complaint Management System 2.0, specifically in the /admin/edit-subcategory.php file. The vulnerability occurs because the 'subcategory' parameter is directly used in SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, enabling unauthorized database operations such as data leakage, tampering, or full system control. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to perform unauthorized database operations, including accessing sensitive data, modifying or deleting data, disrupting services, and potentially gaining full control over the system. Since it is remotely exploitable and publicly disclosed, attackers can easily target vulnerable systems, leading to confidentiality, integrity, and availability breaches. [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 "subcategory" parameter in the /admin/edit-subcategory.php file for SQL injection. A time-based blind SQL injection test can be performed using a payload such as: category=2&subcategory=ABC' RLIKE SLEEP(5)-- MZLZ&submit=. Additionally, the sqlmap tool can be used targeting the "subcategory" parameter to automate detection of the SQL injection vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent execution of malicious SQL code; 2) Implementing strict input validation and filtering on the "subcategory" parameter to ensure only expected input is accepted; 3) Limiting database user permissions by avoiding high-privilege accounts for routine operations to reduce potential damage if exploited. Since no known countermeasures or patches currently exist, replacing the affected component with an alternative product is also suggested. [2, 3]