Skip to main content
CVE-2025-40655VulnerabilityPublished

CVE-2025-40655: Dmacroweb DM Corporative CMS · SQL Injection

Affects Dmacroweb DM Corporative CMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% 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:H/VI:H/VA:H/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 2026-10-26.

What to do

Affected software

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

AI-suggested

Immediate mitigation steps include: 1) Conducting an inventory to identify all instances of DM Corporative CMS in use within the organization. 2) Applying any available vendor patches or updates as soon as they are released. Since no patches are currently available, organizations should implement compensating controls such as: 3) Employing Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the /antcatalogue.asp endpoint and the 'name' parameter. 4) Restricting database user permissions to the minimum necessary, preventing the CMS database account from performing destructive operations if exploited. 5) Implementing input validation and sanitization at the application or proxy level where possible. 6) Monitoring logs for suspicious activity related to the vulnerable endpoint, including unusual query patterns or error messages indicative of injection attempts. 7) Considering temporary disabling or restricting access to the vulnerable functionality until a patch is available. 8) Educating development and security teams about secure coding practices to prevent similar vulnerabilities in the future. These measures should be integrated into a broader vulnerability management and incident response plan.

Description

A SQL injection vulnerability has been found in DM Corporative CMS. This vulnerability allows an attacker to retrieve, create, update and delete databases through the name parameter in /antcatalogue.asp.

References

Community reviews

Loading reviews…