dbcve.org
Dm Corporative CmsApplication · Acc

CVE-2025-40658

HIGH · 7.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 2025.01 or later.
See remediation →
84/100
Remediation priority · High
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
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/selectionnode/framesSelection.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

IDOR vulnerability in DM Corporative CMS allows unauthenticated or unauthorized users to access private administrative areas by manipulating the 'option' parameter (values 0, 1, or 2) in the /administer/selectionnode/framesSelection.asp endpoint. The application fails to validate user authorization before granting access to sensitive administrative functionality.

MitigationImplement proper authorization checks on the framesSelection.asp endpoint to verify user identity and permissions before allowing access to private areas. All sensitive endpoints should validate session authenticity and confirm user role-based access rights.

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
None
Availability
None

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

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. Determine installed CMS version
    Locate the version information for Acc Dm Corporative CMS in the application's administration panel, footer, or in the installation files (such as version.txt, about page, or system info). Compare the found version against the affected range: versions prior to 2025.01 are vulnerable.
    Affected if The installed version is earlier than 2025.01
  2. Verify framesSelection.asp endpoint exists
    Check if the file /administer/selectionnode/framesSelection.asp exists in the web root directory or is accessible via HTTP/HTTPS requests to the server.
    Affected if The endpoint is present and responds to requests
  3. Test option parameter authorization bypass
    Send HTTP GET requests to /administer/selectionnode/framesSelection.asp with different values for the 'option' parameter (0, 1, and 2) without providing valid authentication credentials. Examine the response to determine if administrative interfaces or private areas are accessible without login.
    Affected if Requests with option=0, 1, or 2 return administrative content or private pages without requiring authentication
  4. Inspect application authorization logic
    Review the source code or configuration of framesSelection.asp to verify whether the application performs proper authorization checks on the 'option' parameter before serving sensitive administrative functionality.
    Affected if The endpoint does not validate user permissions before granting access to administrative areas

A system is affected if it runs Acc Dm Corporative CMS version prior to 2025.01 and the /administer/selectionnode/framesSelection.asp endpoint is accessible, allowing the 'option' parameter to be manipulated for unauthorized administrative access.

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 proper authorization checks on the framesSelection.asp endpoint to verify user identity and permissions before allowing access to private areas. All sensitive endpoints should validate session authenticity and confirm user role-based access rights.

Recommended fix Moderate confidence

2025.01

  1. Backup the current DM Corporative CMS installation and database before attempting any upgrade
  2. Download DM Corporative CMS version 2025.01 or later from the official vendor source
  3. Review the upgrade documentation provided with version 2025.01 for any specific migration steps
  4. Deploy the new version to a staging environment first to verify functionality
  5. Apply the upgrade to the production environment
  6. Verify that the vulnerability in /administer/selectionnode/framesSelection.asp is resolved by testing the option parameter with values 0, 1, and 2
  7. Confirm that proper authorization checks are now enforced for the private area access
  8. Monitor the application logs for any unauthorized access attempts

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

Fix this in Dm Corporative Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-40658 — 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-40658 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