CVE-2025-40662

7.5 HIGH

📋 TL;DR

An absolute path disclosure vulnerability in DM Corporative CMS allows attackers to view webroot file contents by accessing non-existent files. This exposes internal server paths and potentially sensitive information. All users of vulnerable DM Corporative CMS versions are affected.

💻 Affected Systems

Products:
  • DM Corporative CMS
Versions: All versions prior to the fix
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: This affects the DMacroWeb component of DM Corporative CMS. The vulnerability is present in default configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could map the server structure, discover sensitive files, and use path information for further attacks like directory traversal or file inclusion.

🟠

Likely Case

Attackers will obtain internal server path information which can aid in reconnaissance for more serious attacks against the web application.

🟢

If Mitigated

With proper web application firewalls and input validation, the impact is limited to information disclosure without direct system compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires no authentication and involves simple HTTP requests to non-existent files. The vulnerability is easy to discover and exploit.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check vendor advisory for specific patched version

Vendor Advisory: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-dm-corporative-cms-dmacroweb

Restart Required: No

Instructions:

1. Review the vendor advisory for patched version. 2. Update DM Corporative CMS to the latest secure version. 3. Verify the fix by testing for the vulnerability.

🔧 Temporary Workarounds

Web Application Firewall Rule

all

Configure WAF to block requests that trigger path disclosure or access non-existent files with specific patterns

Error Page Customization

all

Configure custom error pages that don't reveal path information in error messages

🧯 If You Can't Patch

  • Implement strict input validation to prevent access to non-existent files
  • Configure web server to suppress detailed error messages for 404 responses

🔍 How to Verify

Check if Vulnerable:

Access a non-existent file on the DM Corporative CMS instance and check if the response reveals absolute server paths

Check Version:

Check CMS admin panel or configuration files for version information

Verify Fix Applied:

After patching, attempt to access non-existent files and verify that no path information is disclosed in error responses

📡 Detection & Monitoring

Log Indicators:

  • Multiple 404 errors for non-existent files
  • Requests to unusual file paths
  • Error logs containing full server paths

Network Indicators:

  • HTTP 404 responses containing absolute paths
  • Repeated requests to non-existent file extensions

SIEM Query:

http.status_code=404 AND http.uri CONTAINS ".php" OR http.uri CONTAINS ".asp" AND http.response_body CONTAINS "/var/www/" OR http.response_body CONTAINS "C:\\"

🔗 References

📤 Share & Export