CVE-2025-1959

7.3 HIGH

📋 TL;DR

A critical SQL injection vulnerability exists in Codezips Gym Management System 1.0, specifically in the /change_s_pwd.php file. Attackers can manipulate login_id/login_key parameters to execute arbitrary SQL commands remotely. This affects all installations of Gym Management System 1.0 that expose the vulnerable endpoint.

💻 Affected Systems

Products:
  • Codezips Gym Management System
Versions: 1.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All installations with the vulnerable file accessible are affected. No special configuration required for exploitation.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, privilege escalation, and potential remote code execution via database functions.

🟠

Likely Case

Unauthorized data access, credential theft, and potential system takeover through SQL injection.

🟢

If Mitigated

Limited impact with proper input validation and database permissions restricting damage to non-sensitive data.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit code is publicly available on GitHub, making this easily weaponizable by attackers with minimal technical skill.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None known

Restart Required: No

Instructions:

No official patch available. Consider replacing with alternative software or implementing custom fixes.

🔧 Temporary Workarounds

Web Application Firewall (WAF)

all

Deploy a WAF with SQL injection rules to block malicious requests to /change_s_pwd.php

Input Validation Filter

all

Add server-side input validation to sanitize login_id and login_key parameters

Example PHP: $login_id = mysqli_real_escape_string($conn, $_POST['login_id']);

🧯 If You Can't Patch

  • Block external access to /change_s_pwd.php using firewall rules or web server configuration
  • Implement strict database user permissions with least privilege principle

🔍 How to Verify

Check if Vulnerable:

Test /change_s_pwd.php endpoint with SQL injection payloads like ' OR '1'='1 in login_id parameter

Check Version:

Check software version in admin panel or configuration files

Verify Fix Applied:

Verify that SQL injection payloads no longer execute and return proper error handling

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL errors in application logs
  • Multiple failed login attempts with SQL-like patterns

Network Indicators:

  • HTTP POST requests to /change_s_pwd.php containing SQL keywords (UNION, SELECT, etc.)

SIEM Query:

source="web_logs" AND uri="/change_s_pwd.php" AND (request_body CONTAINS "UNION" OR request_body CONTAINS "SELECT" OR request_body CONTAINS "OR '1'='1'")

🔗 References

📤 Share & Export