# CVE-2026-32867: OPEXUS eComplaint unauthenticated file upload

> Unauthenticated attackers can upload arbitrary files to eComplaint cases by guessing case numbers, leading to data modification and potential storage exhaustion.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-qw9c-jpw9-vj74

## What is CVE-2026-32867?

CVE-2026-32867 is a medium-severity vulnerability in OPEXUS eComplaint, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OPEXUS eComplaint before version 10.1.0.0 allows an unauthenticated attacker to obtain or guess an existing case number and upload arbitrary files via 'Portal/EEOC/DocumentUploadPub.aspx'. Users would see these unexpected files in cases. Uploading a large number of files could consume storage.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-425 (Direct Request)

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

It affects 1 product.


Products: Opexustech Ecase Ecomplaint.

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

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

## Is CVE-2026-32867 being exploited?

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

## Other vulnerabilities in OPEXUS eComplaint

- [CVE-2026-32865](https://insights.sbomify.com/CVE-2026-32865/): OPEXUS eComplaint and eCase insecure password reset (critical 9.2)
- [CVE-2026-22235](https://insights.sbomify.com/CVE-2026-22235/): OPEXUS eComplaint IDOR (high 8.7)
- [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-32867 and fix it if it is affected.

What it is: CVE-2026-32867 is a medium-severity vulnerability in OPEXUS eComplaint, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32867 in the wild and no public exploit code.

Affected product: OPEXUS eComplaint. 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-32867/ (Markdown: https://insights.sbomify.com/CVE-2026-32867/index.md)
```

## Sources

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

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