CVE-2025-11515

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in code-projects Online Complaint Site 1.0 allows remote attackers to manipulate database queries through the cid parameter in /cms/users/register-complaint.php. Attackers can potentially read, modify, or delete database content. All deployments of version 1.0 are affected.

💻 Affected Systems

Products:
  • code-projects Online Complaint Site
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. The vulnerability exists in the default installation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including data theft, data manipulation, and potential server takeover via SQL injection leading to remote code execution.

🟠

Likely Case

Unauthorized data access and extraction of sensitive information from the complaint database, potentially including user credentials and personal information.

🟢

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: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Exploit details are publicly available on GitHub and vuldb. Remote exploitation is possible without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://code-projects.org/

Restart Required: No

Instructions:

1. Check code-projects.org for security updates
2. Apply any available patches
3. Review and sanitize all user inputs in the application

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Implement parameterized queries and input validation for the cid parameter

Modify /cms/users/register-complaint.php to use prepared statements

Web Application Firewall Rules

all

Block SQL injection patterns targeting the vulnerable endpoint

WAF rule: Block requests containing SQL keywords to /cms/users/register-complaint.php

🧯 If You Can't Patch

  • Implement network segmentation to restrict access to the vulnerable application
  • Deploy a web application firewall with SQL injection detection rules

🔍 How to Verify

Check if Vulnerable:

Test the /cms/users/register-complaint.php endpoint with SQL injection payloads in the cid parameter

Check Version:

Check application version in configuration files or about pages

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and return appropriate error messages

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts following SQL injection patterns
  • Unexpected database queries from the application

Network Indicators:

  • HTTP requests to /cms/users/register-complaint.php with SQL keywords in parameters
  • Unusual database connection patterns from the application server

SIEM Query:

source="web_logs" AND uri="/cms/users/register-complaint.php" AND (param="cid" AND value MATCHES "(?i)(union|select|insert|update|delete|drop|create|alter)")

🔗 References

📤 Share & Export