CVE-2025-67806
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 · uneditedThe login mechanism of Sage DPW 2021_06_004 displays distinct responses for valid and invalid usernames, allowing enumeration of existing accounts in versions before 2021_06_000. On-premise administrators can toggle this behavior in newer versions.
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 confidenceSage DPW's login mechanism returns distinguishable error messages or response patterns for valid versus invalid usernames, enabling unauthenticated attackers to enumerate existing user accounts by observing these differential responses.
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= 2025_06_004CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Sage DPW installed versionLocate the version information in the Sage DPW application (typically found in Help > About, or the login page footer, or system information panel)Affected if Version is exactly 2025_06_004
-
Test login response with non-existent usernameAttempt a login using a username that does not exist in the system (e.g., random string like 'testuserxyz123') and record the exact error message or response behavior returnedAffected if Any specific error message is returned (rather than a generic 'invalid credentials' message)
-
Test login response with potentially valid usernameAttempt a login using a known or suspected valid username (e.g., common names like 'admin', 'user') with an incorrect password and record the exact error message or response behaviorAffected if A different error message or response pattern is returned compared to step 2
-
Compare login error messagesReview both responses from steps 2 and 3 - check for differences in message text, timing, HTTP status codes, or any distinguishable pattern between valid and invalid usernamesAffected if The responses differ in any measurable way that reveals whether the username exists in the system
-
Check administrator toggle settingIf you have administrative access to Sage DPW, navigate to the system configuration or security settings panel and look for an option controlling username enumeration or distinct error responsesAffected if The toggle is found and is currently enabled (allowing distinct username responses)
-
Confirm on-premise deployment statusDetermine whether the Sage DPW deployment is on-premise (self-hosted) or cloud-hosted, as the administrator toggle is only available for on-premise installationsAffected if Deployment is on-premise and the administrator toggle for distinct username responses is enabled or not accessible
A user is affected if they are running Sage DPW version 2025_06_004 (or have not disabled the distinct username response behavior via the admin toggle on newer versions) and can observe different login error messages or patterns between valid and invalid usernames.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to Sage DPW version 2021_06_000 or later, or for on-premise deployments, disable the distinct username response behavior via the administrator toggle if already on a newer version.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-67806 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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