CVE-2025-4329

4.3 MEDIUM

📋 TL;DR

This vulnerability in 74CMS allows attackers to perform path traversal attacks by manipulating the 'url' parameter in the download function. Attackers can potentially read arbitrary files on the server by exploiting improper input validation. All users running 74CMS versions up to 3.33.0 are affected.

💻 Affected Systems

Products:
  • 74CMS
Versions: up to 3.33.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All default installations of affected versions are vulnerable. The vulnerability is in the core application code.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could read sensitive system files like /etc/passwd, configuration files, or source code, potentially leading to credential theft, privilege escalation, or further system compromise.

🟠

Likely Case

Attackers read application configuration files, source code, or other sensitive files stored within the web directory, potentially exposing database credentials or other secrets.

🟢

If Mitigated

With proper file permissions and web server configuration, impact is limited to files readable by the web server user within the application directory.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Public exploit code is available. The vulnerability requires no authentication and has simple exploitation steps.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None found

Restart Required: No

Instructions:

1. Check for official patch from 74CMS developers
2. If patch available, apply according to vendor instructions
3. Verify fix by testing the vulnerable endpoint

🔧 Temporary Workarounds

Input Validation Filter

all

Add input validation to filter path traversal sequences from the url parameter

Modify /index.php/index/download/index to validate and sanitize the url parameter before processing

Web Server Restriction

all

Configure web server to restrict file access to specific directories

For Apache: Use mod_rewrite to restrict file access patterns
For Nginx: Use location blocks with deny directives

🧯 If You Can't Patch

  • Implement WAF rules to block path traversal patterns in URL parameters
  • Restrict file system permissions to limit what the web server user can read

🔍 How to Verify

Check if Vulnerable:

Test by accessing /index.php/index/download/index?url=../../../etc/passwd and checking if file contents are returned

Check Version:

Check 74CMS version in admin panel or configuration files

Verify Fix Applied:

Attempt the same test after applying fixes - should receive error or no file contents

📡 Detection & Monitoring

Log Indicators:

  • Multiple requests to /index.php/index/download/index with ../ patterns in parameters
  • Unusual file access patterns from web server process

Network Indicators:

  • HTTP requests containing path traversal sequences (../, ..\) in URL parameters

SIEM Query:

web.url:*../* AND web.path:"/index.php/index/download/index"

🔗 References

📤 Share & Export