# CVE-2026-32869: OPEXUS eComplaint and eCASE XSS via Name of Organization field

> An authenticated attacker can inject XSS payloads via the Organization Name field, potentially hijacking victim sessions in OPEXUS eComplaint and eCASE.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-qx35-58q7-q7x6

## What is CVE-2026-32869?

CVE-2026-32869 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of the "Name of Organization" field when filling out case information. An authenticated attacker can inject an XSS payload which is executed in the context of a victim's session when they visit the case information page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Opexustech Ecase Ecomplaint.

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

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

## Is CVE-2026-32869 being exploited?

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

## Other vulnerabilities in OPEXUS eCASE

- [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-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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32869 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32869 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-32869/ (Markdown: https://insights.sbomify.com/CVE-2026-32869/index.md)
```

## Sources

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

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