CVE-2024-32161

9.8 CRITICAL

📋 TL;DR

jizhiCMS 2.5 contains an unrestricted file upload vulnerability that allows attackers to upload malicious files to the server. This affects all installations of jizhiCMS version 2.5, potentially leading to remote code execution.

💻 Affected Systems

Products:
  • jizhiCMS
Versions: Version 2.5
Operating Systems: Any OS running PHP
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of jizhiCMS 2.5 are vulnerable. No special configuration required.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete server compromise via remote code execution, data theft, and lateral movement within the network.

🟠

Likely Case

Webshell upload leading to website defacement, data exfiltration, and backdoor persistence.

🟢

If Mitigated

File upload attempts blocked or logged, with no successful exploitation.

🌐 Internet-Facing: HIGH - Web applications are directly accessible and vulnerable to unauthenticated attacks.
🏢 Internal Only: MEDIUM - Internal systems could be targeted via phishing or compromised internal accounts.

🎯 Exploit Status

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

Proof-of-concept exploit code is publicly available. Attack requires only web access to the vulnerable endpoint.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: http://jizhicms.com

Restart Required: No

Instructions:

1. Check vendor website for security updates. 2. If no patch available, consider upgrading to a newer version if compatible. 3. Apply workarounds immediately.

🔧 Temporary Workarounds

Restrict File Upload Types

all

Implement server-side validation to only allow specific safe file extensions.

# In PHP upload handler, add: $allowed = ['jpg', 'png', 'gif']; $ext = strtolower(pathinfo($filename, PATHINFO_EXTENSION)); if(!in_array($ext, $allowed)) { die('Invalid file type'); }

Web Application Firewall Rules

linux

Block file uploads to vulnerable endpoints or restrict upload functionality.

# Example mod_security rule: SecRule REQUEST_URI "@contains /upload/" "id:1001,phase:1,deny"

🧯 If You Can't Patch

  • Disable file upload functionality completely in jizhiCMS configuration.
  • Implement network segmentation to isolate the vulnerable system from critical assets.

🔍 How to Verify

Check if Vulnerable:

Attempt to upload a file with a malicious extension (e.g., .php) to the CMS upload endpoint. If successful without validation, system is vulnerable.

Check Version:

# Check jizhiCMS version in admin panel or look for version.txt file

Verify Fix Applied:

Test file upload with restricted extensions. Malicious files should be rejected with proper error messages.

📡 Detection & Monitoring

Log Indicators:

  • Unusual file uploads with executable extensions (.php, .jsp, .asp)
  • Large number of upload requests from single IP
  • Failed upload attempts with suspicious filenames

Network Indicators:

  • POST requests to upload endpoints with unusual file types
  • Traffic spikes to upload functionality

SIEM Query:

source="web_server" AND (uri="*upload*" OR uri="*file*" OR method="POST") AND (file_ext="php" OR file_ext="jsp" OR file_ext="asp")

🔗 References

📤 Share & Export