# CVE-2026-22231: OPEXUS eCASE Audit Document Check Out stored XSS

> Authenticated attackers can inject JavaScript into audit comments, leading to script execution when other users view the action history log.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/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:** 8 Jan 2026
- **Updated:** 8 Jan 2026
- **Also known as:** GHSA-7cgr-2c4h-cvgf

## What is CVE-2026-22231?

CVE-2026-22231 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE Audit, published on 8 Jan 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 eCASE Audit allows an authenticated attacker to save JavaScript as a comment within the Document Check Out functionality. The JavaScript is executed whenever another user views the Action History Log. Fixed in OPEXUS eCASE Platform 11.14.1.0.

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

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

It affects 1 product.


Products: Opexustech Ecase Audit.

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

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

## Is CVE-2026-22231 being exploited?

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

## Other vulnerabilities in OPEXUS eCASE Audit

- [CVE-2026-22230](https://insights.sbomify.com/CVE-2026-22230/): OPEXUS eCASE Audit incorrect access control (high 7.2)
- [CVE-2026-22232](https://insights.sbomify.com/CVE-2026-22232/): OPEXUS eCASE Audit Project Setup stored XSS (medium 4.8)
- [CVE-2026-22233](https://insights.sbomify.com/CVE-2026-22233/): OPEXUS eCASE Audit Project Cost stored XSS (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22231 is a medium-severity cross-site scripting vulnerability in OPEXUS eCASE Audit, published on 8 Jan 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-22231 in the wild and no public exploit code.

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

## Sources

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

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