CVE-2025-5660
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-5660 is a critical SQL injection vulnerability in the PHPGurukul Complaint Management System 2.0, specifically in the /user/register-complaint.php file. The vulnerability occurs because the 'noc' parameter is not properly sanitized or validated before being used in SQL queries. This allows attackers to inject malicious SQL code through the 'noc' input, enabling them to manipulate database queries and perform unauthorized operations such as accessing, modifying, or deleting data. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized access to sensitive data, data leakage, data tampering, full system control by attackers, and disruption of services. Attackers can exploit the flaw remotely to manipulate SQL queries, potentially compromising the confidentiality, integrity, and availability of the system. [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 'noc' parameter in the /user/register-complaint.php endpoint for SQL injection. One method is to use sqlmap, an automated SQL injection tool, targeting the 'noc' parameter with a POST request. Additionally, a proof-of-concept time-based blind SQL injection payload using MySQL's RLIKE operator combined with the SLEEP function can be sent via a multipart/form-data POST request to confirm the vulnerability. Also, Google dorking can be used to identify vulnerable targets by searching for URLs containing 'inurl:user/register-complaint.php'. Example sqlmap command: sqlmap -u "http://target/user/register-complaint.php" --data="noc=1" -p noc --technique=T --batch [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection. 2) Applying rigorous input validation and filtering on the 'noc' parameter to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding elevated privileges for routine operations. If possible, replace the affected component with an alternative product. These steps help prevent exploitation of the SQL injection vulnerability. [2, 3]