# CVE-2026-32865: OPEXUS eComplaint and eCase insecure password reset

> Attackers can reset user passwords and security questions by extracting verification codes from HTTP responses, leading to account takeover.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-54h7-v9wj-85j9

## What is CVE-2026-32865?

CVE-2026-32865 is a critical vulnerability in OPEXUS eCASE, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-32865?

It affects 1 product.


Products: Opexustech Ecase Ecomplaint.

## How do I fix CVE-2026-32865?

No fix has been published for CVE-2026-32865 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32865 being exploited?

There is no known exploitation of CVE-2026-32865 in the wild and no public exploit code.

## Other vulnerabilities in OPEXUS eCASE

- [CVE-2026-22235](https://insights.sbomify.com/CVE-2026-22235/): OPEXUS eComplaint IDOR (high 8.7)
- [CVE-2026-32867](https://insights.sbomify.com/CVE-2026-32867/): OPEXUS eComplaint unauthenticated file upload (medium 5.3)
- [CVE-2026-32866](https://insights.sbomify.com/CVE-2026-32866/): OPEXUS eComplaint and eCase stored XSS via profile first and last name (medium 5.1)
- [CVE-2026-32868](https://insights.sbomify.com/CVE-2026-32868/): OPEXUS eComplaint and eCASE XSS via my information (medium 5.1)
- [CVE-2026-32869](https://insights.sbomify.com/CVE-2026-32869/): OPEXUS eComplaint and eCASE XSS via Name of Organization field (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32865 and fix it if it is affected.

What it is: CVE-2026-32865 is a critical vulnerability in OPEXUS eCASE, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32865 in the wild and no public exploit code.

Affected product: OPEXUS eCASE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32865/ (Markdown: https://insights.sbomify.com/CVE-2026-32865/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32865
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32865
- OSV: https://osv.dev/vulnerability/CVE-2026-32865

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32865/
Summaries are generated and may contain mistakes; the official description above is the record.