CVE-2024-10994

6.3 MEDIUM

📋 TL;DR

This critical vulnerability in Codezips Online Institute Management System 1.0 allows remote attackers to upload arbitrary files via the /edit_user.php endpoint. Attackers can exploit this to upload malicious files like web shells, potentially gaining unauthorized access to the system. All installations of version 1.0 are affected.

💻 Affected Systems

Products:
  • Codezips Online Institute Management System
Versions: 1.0
Operating Systems: Any OS running PHP web server
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations are vulnerable. The vulnerability exists in the image upload functionality of /edit_user.php.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Remote code execution leading to complete system compromise, data theft, and lateral movement within the network.

🟠

Likely Case

Web shell upload enabling persistent backdoor access, file manipulation, and potential privilege escalation.

🟢

If Mitigated

File upload attempts blocked or quarantined with no successful exploitation.

🌐 Internet-Facing: HIGH - Attackers can exploit remotely without authentication.
🏢 Internal Only: MEDIUM - Internal attackers could exploit, but external threat is higher.

🎯 Exploit Status

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

Exploit details are publicly available on GitHub. The vulnerability requires minimal technical skill to exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Consider workarounds or migrating to alternative software.

🔧 Temporary Workarounds

Restrict file uploads

all

Block or disable the /edit_user.php endpoint or implement strict file upload validation

# In web server config (Apache example):
<Location "/edit_user.php">
    Deny from all
</Location>
# In .htaccess:
RewriteRule ^edit_user\.php$ - [F,L]

Implement file upload validation

all

Add server-side validation for uploaded files including file type checking, size limits, and content scanning

# PHP validation example:
$allowed_types = ['image/jpeg', 'image/png', 'image/gif'];
$max_size = 2097152; // 2MB
if (!in_array($_FILES['image']['type'], $allowed_types) || $_FILES['image']['size'] > $max_size) {
    die('Invalid file');
}

🧯 If You Can't Patch

  • Implement web application firewall (WAF) rules to block malicious file uploads
  • Monitor and alert on suspicious file upload activities to /edit_user.php

🔍 How to Verify

Check if Vulnerable:

Test if you can upload non-image files (e.g., .php, .txt) to /edit_user.php endpoint. Check system version in admin panel or source code.

Check Version:

Check admin panel or look for version information in source files, typically in footer or configuration files.

Verify Fix Applied:

Attempt to upload malicious files to /edit_user.php - should be rejected. Verify WAF rules or file validation is working.

📡 Detection & Monitoring

Log Indicators:

  • POST requests to /edit_user.php with file uploads
  • Uploads of non-image file types (.php, .exe, etc.)
  • Large number of failed upload attempts

Network Indicators:

  • Unusual traffic patterns to /edit_user.php
  • File uploads with suspicious extensions

SIEM Query:

source="web_server" AND (uri="/edit_user.php" AND method="POST") AND (file_extension="php" OR file_extension="exe" OR file_extension="sh")

🔗 References

📤 Share & Export