Security readout for executives and security teams
Plain-English summary
Sage DPW 2021_06_004 has a login page that responds differently when a username is valid versus invalid. An attacker on the network can use that difference to figure out which accounts exist, which makes follow-on password guessing or phishing easier. It does not by itself grant access, but it weakens the front door.
Executive priority
Low priority. Address during normal patch and configuration cycles, not as an emergency. Treat it as hygiene that reduces the value of stolen or guessed credentials, and prioritize it higher if the affected portal is internet-facing.
Technical view
The flaw is a username enumeration weakness (CWE-204, Observable Response Discrepancy) in the Sage DPW login mechanism in versions before 2021_06_000. Distinct responses to valid versus invalid usernames let an unauthenticated, network-adjacent attacker harvest account names. CVSS 3.1 base score is 3.7 (AC:H/AV:N/PR:N/UI:N/C:L/I:N/A:N). Per the description, newer on-premise versions allow administrators to toggle the behavior off.
Likely exposure
Limited to organizations running Sage DPW, particularly on-premise deployments where the login page is reachable by attackers or untrusted users. Exposure widens if the portal is internet-facing or used by a large user base whose account naming convention is predictable.
Exploitation context
No active exploitation is cited and the CVE is not on CISA KEV. Attack complexity is rated high and no authentication or user interaction is required. The realistic threat is reconnaissance feeding credential stuffing, password spraying, or targeted phishing rather than direct compromise.
Researcher notes
Source bundle does not enumerate specific affected SKUs or fixed builds beyond the 2021_06_000 boundary, and one reference is a Pastebin link that should be treated cautiously. The CVSS vector (AC:H, C:L only) reflects information disclosure with non-trivial preconditions. Chain this with weak password policies or absent MFA when modeling realistic risk.
Mitigation direction
- Upgrade Sage DPW to a version at or after 2021_06_000 that exposes the enumeration toggle.
- On supported versions, enable the administrator setting that suppresses distinct login responses.
- Restrict portal reachability to VPN, SSO, or allow-listed networks where feasible.
- Enforce account lockout, MFA, and rate limiting on the login endpoint.
- Confirm vendor guidance with Sage DPW support before changing production settings.
Validation and detection
- Inventory Sage DPW instances and record build numbers against the 2021_06_000 threshold.
- From an unauthenticated session, compare login responses for known-valid and clearly-invalid usernames and note timing or message differences.
- Review web server and WAF logs for high-volume login attempts that iterate usernames.
- After remediation, repeat the comparison test and confirm responses are uniform.
- Document findings and residual risk in the vulnerability tracker.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-204: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-67806 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N2.21.4mitreVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.sagedpw.at/CVE reference, mitre
- https://pastebin.com/Tk4LgMG2CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Response Discrepancy
Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.