CVE-2025-10851

7.3 HIGH

📋 TL;DR

CVE-2025-10851 is an SQL injection vulnerability in Campcodes Gym Management System 1.0 that allows remote attackers to execute arbitrary SQL commands via the Username parameter in the /ajax.php?action=login endpoint. This affects all installations of Campcodes Gym Management System 1.0 that expose the vulnerable endpoint.

💻 Affected Systems

Products:
  • Campcodes Gym Management System
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations are vulnerable as the flaw exists in core authentication code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise including authentication bypass, data exfiltration, privilege escalation, and potential remote code execution if database functions allow it.

🟠

Likely Case

Authentication bypass leading to unauthorized system access, data theft of member information, and potential manipulation of gym management data.

🟢

If Mitigated

Limited impact if proper input validation and WAF rules are in place, though SQL injection attempts may still be logged.

🌐 Internet-Facing: HIGH - The vulnerability is remotely exploitable and the exploit is publicly available, making internet-facing instances immediate targets.
🏢 Internal Only: MEDIUM - Internal systems are still vulnerable but require network access; risk increases if internal users can access the vulnerable endpoint.

🎯 Exploit Status

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

Exploit code is publicly available and targets a common SQL injection pattern in authentication endpoints.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates. Consider implementing parameterized queries and input validation in the /ajax.php login handler.

🔧 Temporary Workarounds

Web Application Firewall Rule

all

Implement WAF rules to block SQL injection patterns in the Username parameter

# Example ModSecurity rule: SecRule ARGS:Username "@detectSQLi" "id:1001,phase:2,deny,status:403"

Input Validation Filter

linux

Add server-side validation to reject suspicious characters in Username field

# PHP example: if(preg_match('/[\'\"\;\-\#\*]/', $_POST['Username'])) { die('Invalid input'); }

🧯 If You Can't Patch

  • Isolate the system behind a reverse proxy with strict input validation
  • Implement network segmentation to limit access to the vulnerable endpoint

🔍 How to Verify

Check if Vulnerable:

Test the /ajax.php?action=login endpoint with SQL injection payloads in the Username parameter (e.g., admin' OR '1'='1)

Check Version:

Check the system's about page or configuration files for version information

Verify Fix Applied:

Verify that SQL injection attempts return error messages or are blocked, and that parameterized queries are implemented

📡 Detection & Monitoring

Log Indicators:

  • SQL syntax errors in web server logs
  • Multiple failed login attempts with special characters
  • Unusual database queries from web application

Network Indicators:

  • HTTP POST requests to /ajax.php with SQL keywords in parameters
  • Unusual traffic patterns to login endpoint

SIEM Query:

source="web_logs" AND (url="/ajax.php" AND (param="Username" AND value MATCHES "[';\-]|OR|UNION|SELECT"))

🔗 References

📤 Share & Export