CVE-2025-7123

4.7 MEDIUM

📋 TL;DR

This critical SQL injection vulnerability in Campcodes Complaint Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the cid/uid parameters in /admin/complaint-details.php. Organizations using this software are affected, potentially leading to data theft, system compromise, or complete database takeover.

💻 Affected Systems

Products:
  • Campcodes Complaint Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation and requires the admin interface to be accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data exfiltration, privilege escalation to administrative access, and potential remote code execution on the underlying server.

🟠

Likely Case

Unauthorized access to sensitive complaint data, user information disclosure, and potential manipulation of system records.

🟢

If Mitigated

Limited impact with proper input validation and database permissions, potentially only error messages or partial data exposure.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit requires admin access but SQL injection is straightforward once authenticated. Public exploit code is available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider implementing input validation and parameterized queries in the affected PHP file.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add input validation and parameterized queries to /admin/complaint-details.php to prevent SQL injection.

Modify PHP code to use prepared statements with PDO or mysqli

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection protection rules to block malicious requests.

Configure WAF rules to block SQL injection patterns

🧯 If You Can't Patch

  • Restrict access to /admin/complaint-details.php to specific IP addresses or networks
  • Implement database user with minimal privileges and enable query logging for suspicious activity

🔍 How to Verify

Check if Vulnerable:

Test the /admin/complaint-details.php endpoint with SQL injection payloads in cid/uid parameters (e.g., ' OR '1'='1).

Check Version:

Check the software version in the system interface or configuration files.

Verify Fix Applied:

Attempt SQL injection after implementing fixes; successful protection should return normal responses without database errors or unexpected data.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL queries in database logs
  • Multiple failed login attempts followed by SQL injection patterns
  • Admin access logs showing suspicious parameter values

Network Indicators:

  • HTTP requests to /admin/complaint-details.php with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/admin/complaint-details.php" AND (param="cid" OR param="uid") AND (value="*OR*" OR value="*UNION*" OR value="*SELECT*" OR value="*INSERT*")

🔗 References

📤 Share & Export