CVE-2025-11591

6.3 MEDIUM

📋 TL;DR

This SQL injection vulnerability in CodeAstro Gym Management System 1.0 allows attackers to manipulate database queries through the /admin/actions/delete-member.php endpoint. Attackers can potentially read, modify, or delete sensitive data in the database. All installations of version 1.0 with the vulnerable file are affected.

💻 Affected Systems

Products:
  • CodeAstro Gym Management System
Versions: 1.0
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: Requires the /admin/actions/delete-member.php file to be present and accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database compromise leading to data theft, data destruction, or full system takeover via SQL injection to RCE escalation.

🟠

Likely Case

Unauthorized access to sensitive member data, administrative credentials theft, or database manipulation affecting business operations.

🟢

If Mitigated

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

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit disclosed publicly on GitHub, requires admin access to reach vulnerable endpoint.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: UNKNOWN

Vendor Advisory: https://codeastro.com/

Restart Required: No

Instructions:

1. Check vendor website for security updates. 2. If no patch available, implement parameterized queries in delete-member.php. 3. Validate and sanitize all user inputs before database operations.

🔧 Temporary Workarounds

Input Validation and Sanitization

all

Add server-side validation to sanitize ID parameter before processing SQL queries.

Implement prepared statements with parameterized queries in PHP code

Access Restriction

all

Restrict access to /admin/actions/delete-member.php using web server configuration.

Add 'Deny from all' to .htaccess for the directory or use IP whitelisting

🧯 If You Can't Patch

  • Implement WAF rules to block SQL injection patterns targeting the vulnerable endpoint
  • Monitor and alert on suspicious database queries from the application

🔍 How to Verify

Check if Vulnerable:

Test the /admin/actions/delete-member.php endpoint with SQL injection payloads in the ID parameter.

Check Version:

Check system version in admin panel or configuration files

Verify Fix Applied:

Verify that parameterized queries are implemented and SQL injection attempts no longer succeed.

📡 Detection & Monitoring

Log Indicators:

  • Unusual SQL error messages in application logs
  • Multiple failed delete operations with malformed IDs
  • Admin actions from unexpected IP addresses

Network Indicators:

  • HTTP POST requests to /admin/actions/delete-member.php with SQL payloads in parameters

SIEM Query:

source="web_logs" AND uri_path="/admin/actions/delete-member.php" AND (query_string="*sql*" OR query_string="*union*" OR query_string="*select*" OR query_string="*sleep*")

🔗 References

📤 Share & Export