CVE-2025-10786

7.3 HIGH

📋 TL;DR

This SQL injection vulnerability in Campcodes Grocery Sales and Inventory System 1.0 allows attackers to execute arbitrary SQL commands via the ID parameter in the /ajax.php?action=delete_user endpoint. The vulnerability is remotely exploitable and affects all deployments of version 1.0. Attackers could potentially access, modify, or delete database contents.

💻 Affected Systems

Products:
  • Campcodes Grocery Sales and Inventory System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations of version 1.0 are vulnerable. The system appears to be a PHP/MySQL web application.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, authentication bypass, and potential remote code execution if database permissions allow.

🟠

Likely Case

Unauthorized data access, privilege escalation, and potential data manipulation affecting inventory, sales, and user data.

🟢

If Mitigated

Limited impact with proper input validation, parameterized queries, and database permission restrictions in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available. Attack requires access to the delete_user function, suggesting some authentication may be needed.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://www.campcodes.com/

Restart Required: No

Instructions:

No official patch available. Consider implementing parameterized queries in /ajax.php for the delete_user action, specifically for the ID parameter.

🔧 Temporary Workarounds

Input Validation Filter

all

Add server-side validation to ensure ID parameter contains only numeric values

In PHP: if(!is_numeric($_GET['ID'])) { die('Invalid input'); }

Web Application Firewall Rule

all

Block SQL injection patterns targeting the delete_user endpoint

WAF rule to detect SQL patterns in /ajax.php?action=delete_user parameters

🧯 If You Can't Patch

  • Restrict network access to the application using firewall rules
  • Implement database user with minimal permissions (read-only where possible)

🔍 How to Verify

Check if Vulnerable:

Test the /ajax.php?action=delete_user endpoint with SQL injection payloads in the ID parameter

Check Version:

Check application version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection attempts no longer succeed and that input validation is properly implemented

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple delete_user requests with malformed ID parameters
  • Database error messages containing SQL syntax

Network Indicators:

  • HTTP requests to /ajax.php?action=delete_user with SQL keywords in parameters
  • Unusual database connection patterns from web server

SIEM Query:

source="web_logs" AND uri="/ajax.php" AND query="action=delete_user" AND (param="ID" AND value MATCHES "(?i)(union|select|insert|update|delete|drop|--|#|/*)")

🔗 References

📤 Share & Export