dbcve.org
Sage DpwApplication · Sagedpw

CVE-2025-67805

HIGH · 7.5 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A non-default configuration in Sage DPW 2025_06_004 allows unauthenticated access to diagnostic endpoints within the Database Monitor feature, exposing sensitive information such as hashes and table names. This feature is disabled by default in all installations and never available in Sage DPW Cloud. It was forcibly disabled again in version 2025_06_003.

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 non-default configuration in Sage DPW allows unauthenticated remote attackers to access diagnostic endpoints within the Database Monitor feature, exposing sensitive system information including password hashes and database table names.

MitigationEnsure the Database Monitor feature remains disabled in configuration, or update to version 2025_06_003 or later where the feature has been forcibly disabled.

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
Sage DpwApplication
Affected:= 2025_06_004

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. Identify installed Sage DPW version
    Locate the Sage DPW version information through the application's About dialog, version file, or installer history. Common locations include the application help menu, installation directory metadata, or system registry.
    Affected if The installed version is exactly 2025_06_004 (the vulnerable release). Versions before 2025_06_004 or at 2025_06_003 and later are not affected by this specific CVE.
  2. Locate Database Monitor configuration
    Access the Sage DPW administrative or configuration interface where feature settings are managed. Look for settings related to Database Monitor, diagnostics, or monitoring features.
    Affected if The Database Monitor feature is currently enabled (switched on) in the configuration.
  3. Verify Database Monitor accessibility
    If network-accessible, attempt to reach the diagnostic endpoints typically associated with Database Monitor functionality. Check whether unauthenticated requests to these endpoints return system information.
    Affected if Unauthenticated access to Database Monitor diagnostic endpoints is possible and returns sensitive data such as password hashes or database table structures.
  4. Review recent configuration changes
    Examine configuration logs or audit trails for any changes to Database Monitor settings, particularly any enablement events that may have occurred after initial installation.
    Affected if Database Monitor was explicitly enabled at any point after installation.

You are affected if running Sage DPW version 2025_06_004 with the Database Monitor feature enabled, allowing unauthenticated access to sensitive diagnostic data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure the Database Monitor feature remains disabled in configuration, or update to version 2025_06_003 or later where the feature has been forcibly disabled.

Recommended fix Moderate confidence

Any Sage DPW version higher than 2025_06_004 that includes the security fix (contact Sage support for exact version)

  1. 1. Verify current Sage DPW installation version by checking the application or system information panel
  2. 2. Contact Sage support or check official release notes to obtain the fixed version (version higher than 2025_06_004 that includes the patch)
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Back up the current Sage DPW configuration and database according to standard backup procedures
  5. 5. Apply the upgrade to the latest Sage DPW release that addresses CVE-2025-67805
  6. 6. After upgrade, verify that the Database Monitor feature diagnostic endpoints are not accessible without authentication
  7. 7. Confirm the fix by reviewing release notes or patch documentation for CVE-2025-67805
Caveat Standard upgrade risks apply - test in non-production environment first

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

Fix this in Sage Dpw Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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