# CVE-2026-22234: OPEXUS eCasePortal unauthenticated IDOR

> Unauthenticated attackers can access, delete, or upload files by manipulating form IDs in the OPEXUS eCasePortal application.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 8 Jan 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-rw5g-57c7-74m2

## What is CVE-2026-22234?

CVE-2026-22234 is a critical missing authorization vulnerability in OPEXUS eCase Portal, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OPEXUS eCasePortal before version 9.0.45.0 allows an unauthenticated attacker to navigate to the 'Attachments.aspx' endpoint, iterate through predictable values of 'formid', and download or delete all user-uploaded files, or upload new files.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Opexustech Ecase Portal.

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

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

## Is CVE-2026-22234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22234 is a critical missing authorization vulnerability in OPEXUS eCase Portal, published on 8 Jan 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-22234 in the wild and no public exploit code.

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

## Sources

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

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