CVE-2025-10851
7.3Campcodes · Gym Management System
Campcodes Gym Management System 1.0 is vulnerable to remote SQL injection via the Username argument in the ajax.php login function, allowing unauthenticated attackers to manipulate database queries.
Executive summary
An unauthenticated SQL injection vulnerability in Campcodes Gym Management System 1.0 poses a significant risk of unauthorized data access and potential system compromise.
Vulnerability
This vulnerability is a SQL injection (CWE-89) flaw located in the /ajax.php endpoint. An unauthenticated attacker can supply malicious input to the Username parameter to execute arbitrary SQL commands against the backend database.
Business impact
The ability for an unauthenticated user to interact directly with the database poses a severe threat to data confidentiality and integrity. With a CVSS score of 7.3, this high-severity flaw could lead to the unauthorized exfiltration of user credentials or sensitive gym member information, potentially resulting in regulatory non-compliance and reputational damage.
Remediation
Immediate Action: As no official patch is currently available, administrators should restrict network access to the application or disable the affected login functionality if possible.
Proactive Monitoring: Monitor database query logs for unusual syntax patterns, such as UNION or SLEEP commands, and review web server access logs for repeated requests to the ajax.php endpoint.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection payloads targeting the Username parameter.
Exploitation status
Public Exploit Available: Yes, a published proof-of-concept exists and is attributed to the technical write-up provided in the reference documentation.
Analyst recommendation
Given the availability of a public proof-of-concept and the ease of exploitation, this vulnerability requires immediate attention. Organizations utilizing Campcodes Gym Management System 1.0 must prioritize the implementation of compensating controls, such as WAF filtering, while maintaining close contact with the vendor for an official security update.
Sources
Originally found and disclosed by liule960117 (VulDB User), per the CVE Program record.