CVE-2025-7120
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-7120 is a critical SQL injection vulnerability in version 1.0 of the Campcodes Complaint Management System, specifically in the /users/check_availability.php file. The vulnerability occurs because the 'email' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code directly into database queries. This flaw enables unauthorized manipulation of the database without requiring authentication, making it highly accessible to attackers. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, allowing attackers to retrieve sensitive information, modify or delete data, disrupt services, and potentially achieve full system compromise. This threatens system security, data integrity, and business continuity. [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 'email' parameter in the /users/check_availability.php endpoint for SQL injection. Common techniques include boolean-based blind SQL injection, error-based SQL injection, and time-based blind SQL injection. Tools like sqlmap can be used to automate detection. Example payloads include: - Boolean-based: email=123' OR NOT 3035=3035 # - Error-based: email=123' OR (SELECT 8304 FROM(SELECT COUNT(*),CONCAT(0x716a766271,(SELECT (ELT(8304=8304,1))),0x7162627a71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)-- - Time-based: email=123' AND (SELECT 9108 FROM (SELECT(SLEEP(5)))nghL)-- A sample sqlmap command to test the vulnerability could be: sqlmap -u "http://target.com/users/check_availability.php?email=test" --batch --dbs [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Implement prepared statements with parameter binding to prevent SQL injection. 2. Enforce strict input validation and filtering on the 'email' parameter to ensure it conforms to expected formats. 3. Minimize database user privileges by avoiding use of high-privilege accounts for routine database operations. 4. Conduct regular security audits of code and systems to detect and fix vulnerabilities promptly. If possible, consider replacing the affected component with an alternative product as no known countermeasures are documented. [1, 3, 2]