CVE-2025-7123
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-7123 is a critical SQL injection vulnerability in Campcodes Complaint Management System version 1.0, specifically in the /admin/complaint-details.php file. The vulnerability arises because the parameters 'cid' and 'uid' are not properly validated or sanitized before being used in SQL queries. This allows an attacker, who must be authenticated with backend access, to inject malicious SQL code remotely. Exploiting this flaw can lead to unauthorized database access, enabling attackers to retrieve, modify, or delete sensitive data, potentially gaining full control over the system. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can severely impact you by allowing attackers to perform unauthorized actions on your database, including accessing sensitive information, modifying or deleting data, and potentially taking full control of the system. It can lead to data leakage, data tampering, service disruption, and compromise of system integrity and availability, which can affect business continuity and security. [1, 2, 3, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /admin/complaint-details.php endpoint for SQL injection on the 'cid' and 'uid' parameters. One can use tools like sqlmap with an authenticated session cookie (PHPSESSID) obtained by logging into the backend system (default credentials: admin/admin). Example sqlmap command: sqlmap -u "http://target/admin/complaint-details.php?cid=1" --cookie="PHPSESSID=your_session_id" --risk=3 --level=5 --technique=BEUSTQ. Additionally, Google dorking with queries like 'inurl:admin/complaint-details.php' can help identify vulnerable targets. [3, 4]
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 'cid' and 'uid' parameters, minimizing database user permissions by avoiding use of high-privilege accounts for routine operations, and conducting regular security audits. If possible, replacing the affected component with an alternative product is recommended. [3, 4]