CVE-2025-40660

7.5 HIGH

📋 TL;DR

An Insecure Direct Object Reference (IDOR) vulnerability in DM Corporative CMS allows attackers to bypass authentication and access private admin areas by manipulating URL parameters. This affects all organizations using vulnerable versions of DM Corporative CMS, potentially exposing sensitive administrative functions and data.

💻 Affected Systems

Products:
  • DM Corporative CMS
Versions: All versions prior to patch
Operating Systems: Windows, Linux
Default Config Vulnerable: ⚠️ Yes
Notes: Affects web applications running DM Corporative CMS with the vulnerable /administer/select node/data.asp endpoint accessible.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of administrative functions, unauthorized access to sensitive data, privilege escalation, and potential lateral movement within the system.

🟠

Likely Case

Unauthorized access to administrative interfaces, exposure of sensitive configuration data, and potential manipulation of CMS content.

🟢

If Mitigated

Limited impact with proper authentication controls, but still represents an authentication bypass vulnerability.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires simple URL parameter manipulation without authentication. The vulnerability is publicly documented with specific exploitation details.

🛠️ 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: Yes

Instructions:

1. Review vendor advisory for patch details. 2. Apply the latest security update from DM Corporative. 3. Restart the web application service. 4. Verify the fix by testing the vulnerable endpoint.

🔧 Temporary Workarounds

Web Application Firewall Rule

all

Block requests to the vulnerable endpoint with specific parameter patterns

WAF specific - configure rule to block: /administer/select node/data.asp?mode=catalogue&id1=1&id2=1session=&cod=1&networks=0 with option parameter values 0,1,2

Access Restriction

all

Restrict access to the vulnerable endpoint using network controls

iptables -A INPUT -p tcp --dport 80 -m string --string "/administer/select" --algo bm -j DROP
netsh advfirewall firewall add rule name="Block DM CMS Vuln" dir=in action=block program="%SystemRoot%\System32\inetsrv\w3wp.exe" remoteip=any

🧯 If You Can't Patch

  • Implement strict authentication and authorization checks for all administrative endpoints
  • Deploy a web application firewall with rules specifically blocking exploitation patterns for this vulnerability

🔍 How to Verify

Check if Vulnerable:

Attempt to access /administer/select node/data.asp?mode=catalogue&id1=1&id2=1session=&cod=1&networks=0 with option=0,1,2 parameters. If access is granted without proper authentication, the system is vulnerable.

Check Version:

Check CMS version in administrative interface or consult vendor documentation for version identification methods.

Verify Fix Applied:

Repeat the vulnerable URL access attempts. Proper authentication should now be required, and unauthorized access attempts should be blocked or redirected to login.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed authentication attempts followed by successful access to /administer/select node/data.asp
  • Access to administrative endpoints from unexpected IP addresses
  • URL parameters containing option=0, option=1, or option=2 in requests to the vulnerable endpoint

Network Indicators:

  • Unusual traffic patterns to administrative endpoints
  • HTTP requests with manipulated parameter values bypassing authentication

SIEM Query:

source="web_server" AND (url="/administer/select node/data.asp" AND (param="option=0" OR param="option=1" OR param="option=2"))

🔗 References

📤 Share & Export