| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 1.61+ |
Summary
A vulnerability labeled as problematic has been found in Sage DPW 2025_06_004. Impacted is an unknown function of the component Login. Executing a manipulation can lead to response discrepancy. This vulnerability is registered as CVE-2025-67807. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic was found in Sage DPW 2025_06_004. This vulnerability affects an unknown part of the component Login. The manipulation with an unknown input leads to a response discrepancy vulnerability. The CWE definition for the vulnerability is CWE-204. The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere. As an impact it is known to affect confidentiality. CVE summarizes:
The login mechanism of Sage DPW 2025_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 behaviour in newer versions.
This vulnerability was named CVE-2025-67807 since 12/12/2025. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Response discrepancyCWE: CWE-204 / CWE-203 / CWE-200
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/12/2025 CVE reserved04/01/2026 Advisory disclosed
04/01/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2025-67807 (🔒)
GCVE (CVE): GCVE-0-2025-67807
GCVE (VulDB): GCVE-100-354700
Entry
Created: 04/01/2026 18:06Changes: 04/01/2026 18:06 (52)
Complete: 🔍
Cache ID: 216:1E4:103
No comments yet. Languages: en.
Please log in to comment.