OPEXUS eComplaint/eCASE prior 10.1.0.0 Verification Code ForcePasswordReset.aspx password recovery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in OPEXUS eComplaint and eCASE. Affected is an unknown function of the file ForcePasswordReset.aspx of the component Verification Code Handler. Executing a manipulation can lead to password recovery. The identification of this vulnerability is CVE-2026-32865. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in OPEXUS eComplaint and eCASE and classified as problematic. This vulnerability affects some unknown functionality of the file ForcePasswordReset.aspx of the component Verification Code Handler. The manipulation with an unknown input leads to a password recovery vulnerability. The CWE definition for the vulnerability is CWE-640. The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak. As an impact it is known to affect integrity. CVE summarizes:
OPEXUS eComplaint and eCASE before version 10.1.0.0 include the secret verification code in the HTTP response when requesting a password reset via 'ForcePasswordReset.aspx'. An attacker who knows an existing user's email address can reset the user's password and security questions. Existing security questions are not asked during the process.
The advisory is shared for download at raw.githubusercontent.com. This vulnerability was named CVE-2026-32865 since 03/16/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1552.
By approaching the search of inurl:ForcePasswordReset.aspx it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 10.1.0.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 9.8
CNA Vector (cisa-cg): 🔒
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: Password recoveryCWE: CWE-640
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: eComplaint/eCASE 10.1.0.0
Timeline
03/16/2026 CVE reserved03/19/2026 Advisory disclosed
03/19/2026 VulDB entry created
03/30/2026 VulDB entry last update
Sources
Advisory: raw.githubusercontent.comStatus: Confirmed
CVE: CVE-2026-32865 (🔒)
GCVE (CVE): GCVE-0-2026-32865
GCVE (VulDB): GCVE-100-351724
Entry
Created: 03/19/2026 17:26Updated: 03/30/2026 16:36
Changes: 03/19/2026 17:26 (76), 03/24/2026 01:16 (1), 03/30/2026 16:36 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.