CVE-2025-1166

6.3 MEDIUM

📋 TL;DR

CVE-2025-1166 is a critical unrestricted file upload vulnerability in SourceCodester Food Menu Manager 1.0. Attackers can remotely upload arbitrary files to the endpoint/update.php endpoint, potentially leading to remote code execution. All users of Food Menu Manager 1.0 are affected.

💻 Affected Systems

Products:
  • SourceCodester Food Menu Manager
Versions: 1.0
Operating Systems: All platforms running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: The vulnerability exists in the default installation. No special configuration is required for exploitation.

📦 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

Webshell deployment allowing persistent backdoor access, data exfiltration, and further exploitation of the server.

🟢

If Mitigated

File uploads blocked or restricted, preventing exploitation but potentially disrupting legitimate functionality.

🌐 Internet-Facing: HIGH - Attackers can exploit remotely without authentication, making internet-facing instances immediate targets.
🏢 Internal Only: MEDIUM - Internal attackers or compromised internal systems could exploit, but requires network access.

🎯 Exploit Status

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

Public exploit code is available, making exploitation trivial for attackers with basic skills.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

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

Restart Required: No

Instructions:

No official patch available. Check vendor website for updates. Consider removing or replacing the software.

🔧 Temporary Workarounds

Restrict file uploads via web server

all

Configure web server to block access to endpoint/update.php or restrict file uploads to specific extensions.

# Apache: Add to .htaccess
<Files "update.php">
    Order Allow,Deny
    Deny from all
</Files>
# Nginx: Add to server block
location ~ /endpoint/update\.php$ {
    deny all;
}

Implement file validation

all

Add server-side validation to restrict uploaded file types to only allowed extensions (e.g., .jpg, .png).

# PHP example
$allowed = ['jpg', 'png', 'gif'];
$ext = strtolower(pathinfo($_FILES['file']['name'], PATHINFO_EXTENSION));
if (!in_array($ext, $allowed)) {
    die('Invalid file type');
}

🧯 If You Can't Patch

  • Remove or disable the endpoint/update.php file from the web directory.
  • Implement a Web Application Firewall (WAF) with rules to block file upload exploits targeting this endpoint.

🔍 How to Verify

Check if Vulnerable:

Check if endpoint/update.php exists in the web root and test if it accepts file uploads without proper validation.

Check Version:

Check the software version in the admin panel or readme files; vulnerable if version is 1.0.

Verify Fix Applied:

Attempt to upload a malicious file (e.g., .php shell) to endpoint/update.php; successful blocking indicates fix.

📡 Detection & Monitoring

Log Indicators:

  • Unusual POST requests to endpoint/update.php with file uploads
  • Uploads of files with suspicious extensions (.php, .jsp, .asp)
  • Increased error logs from file validation failures

Network Indicators:

  • HTTP POST traffic to /endpoint/update.php with file uploads
  • Outbound connections from the server after file upload

SIEM Query:

source="web_logs" AND uri="/endpoint/update.php" AND method="POST" AND file_upload=true

🔗 References

📤 Share & Export