dbcve.org
Dm Corporative CmsApplication · Acc

CVE-2025-40654

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 2025.01 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 and cod parameters in /antbuspre.asp.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL injection vulnerability exists in DM Corporative CMS within the /antbuspre.asp endpoint. The 'name' and 'cod' parameters are not properly sanitized before being used in SQL queries, allowing attackers to inject malicious SQL statements. This enables complete database compromise including unauthorized read, write, and delete operations.

MitigationImplement parameterized queries or prepared statements for all database interactions in /antbuspre.asp, and apply input validation/sanitization on the 'name' and 'cod' parameters before SQL execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dm Corporative CmsApplication
Affected:< 2025.01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if DM Corporative CMS is installed
    Look for the application in your web server's document root or check for DM Corporative CMS files. Common paths may include /, /dm_corporative, or /cms directories. Check for presence of .asp files typical to this CMS.
    Affected if The CMS is present and running on the server
  2. Determine the installed version
    Check for a version file, footer in the admin panel, or version information in the source code. Common locations include a /version.txt, /about.asp, or check the main index page source for version strings.
    Affected if The version is lower than 2025.01 or cannot be determined (treat unknown versions below 2025.01 as affected)
  3. Verify the vulnerable endpoint exists
    Check if the file /antbuspre.asp exists in the web root. This can be done by attempting to access the URL directly or listing files in the web directory.
    Affected if The file /antbuspre.asp exists and is accessible via HTTP/HTTPS
  4. Confirm the name and cod parameters are accepted
    Send a test request to /antbuspre.asp with the name parameter (for example, name=test) and verify the application processes it without error or proper sanitization. Check if the application returns SQL-related errors.
    Affected if The application accepts and processes the name or cod parameters without proper SQL injection protection

If DM Corporative CMS version is below 2025.01 and the /antbuspre.asp endpoint exists and accepts name or cod parameters, the system is affected by this SQL injection vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.01 or later
Fixed in 2025.01
Interim mitigation

Implement parameterized queries or prepared statements for all database interactions in /antbuspre.asp, and apply input validation/sanitization on the 'name' and 'cod' parameters before SQL execution.

Recommended fix Moderate confidence

2025.01

  1. 1. Confirm the current version of DM Corporative CMS is below 2025.01
  2. 2. Review the application changelog or release notes for version 2025.01 to understand changes
  3. 3. Create a backup of the current database and application files
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Deploy version 2025.01 or later of DM Corporative CMS
  6. 6. Verify the SQL injection vulnerability is resolved by testing the /antbuspre.asp endpoint with the name and cod parameters
  7. 7. Monitor application logs for any errors after upgrade
Caveat Review CMS release notes for any breaking changes between current version and 2025.01

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dm Corporative Cms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40654 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-40654 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data