CVE-2025-7121
BaseFortify
Publication date: 2025-07-07
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| campcodes | complaint_management_system | 1.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-7121 is a critical SQL injection vulnerability in Campcodes Complaint Management System version 1.0, specifically in the file /users/complaint-details.php. The vulnerability occurs because the 'cid' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to retrieve, modify, or delete sensitive data. The flaw can be exploited remotely and does not require user interaction, making it a serious security risk. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, resulting in data leakage, modification, or deletion of sensitive information. It can compromise the confidentiality, integrity, and availability of the system. Attackers may also achieve full system compromise or disrupt services. Since the vulnerability can be exploited remotely and easily, it poses a significant risk to the security and stability of affected systems. [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 checking for the presence of the vulnerable endpoint '/users/complaint-details.php' and testing the 'cid' parameter for SQL injection. One method is to use Google dorking with the query 'inurl:users/complaint-details.php' to identify potentially vulnerable targets. For active testing, you can use tools like curl or sqlmap to send crafted requests to the 'cid' parameter and observe if SQL injection is possible. Example curl command: curl -v 'http://target/users/complaint-details.php?cid=1' and then try injecting SQL payloads such as '1 OR 1=1'. Automated tools like sqlmap can be used as: sqlmap -u 'http://target/users/complaint-details.php?cid=1' --batch. Note that exploitation requires authentication (valid PHPSESSID), so testing should be done with valid session credentials. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements or parameterized queries to ensure the 'cid' parameter is treated strictly as data, preventing SQL injection. 2) Applying strict input validation and filtering on the 'cid' parameter to allow only expected formats (e.g., numeric values). 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine database operations. 4) Conducting regular security audits to detect and remediate vulnerabilities promptly. If possible, replace the affected component with a secure alternative. Additionally, restrict access to the vulnerable endpoint and monitor for suspicious activity until a patch or fix is applied. [2, 1, 3]