Skip to main content
VulnerabilityPublished

CVE-2025-40660: Dmacroweb DM Corporative CMS · Insecure Direct Object Reference

Affects Dmacroweb DM Corporative CMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Dmacroweb DM Corporative CMSAffected
  • =0
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should implement compensating controls immediately. These include: 1) Restricting access to the /administer/select node/data.asp endpoint via network-level controls such as IP whitelisting or VPN-only access to administrative interfaces. 2) Implementing web application firewalls (WAFs) with custom rules to detect and block requests manipulating the 'option' parameter with unauthorized values. 3) Conducting thorough access control reviews and hardening authorization logic within the CMS if source code or configuration access is available. 4) Monitoring web server logs for suspicious requests targeting the vulnerable endpoint and unusual parameter values. 5) Isolating the CMS environment from public networks where feasible. 6) Engaging with the vendor for updates or patches and planning for timely application once available. 7) Educating administrators about the vulnerability and enforcing strong operational security practices to detect and respond to potential exploitation attempts.

Description

An Insecure Direct Object Reference (IDOR) vulnerability has been found in DM Corporative CMS. This vulnerability allows an attacker to access the private area setting the option parameter equal to 0, 1 or 2 in /administer/select node/data.asp?mode=catalogue&id1=1&id2=1session=&cod=1&networks=0.

References

Community reviews

Loading reviews…