# CVE-2022-39172: Cross-site scripting in n/a

> A stored XSS in openVIVA c2 allows authenticated attackers to execute arbitrary code in victims' browsers via the process name field.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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:** 30 Oct 2023
- **Updated:** 9 Sep 2024
- **Also known as:** GHSA-92m3-4hrq-4449

## What is CVE-2022-39172?

CVE-2022-39172 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A stored XSS in the process overview (bersicht zugewiesener Vorgaenge) in mbsupport openVIVA c2 20220101 allows a remote, authenticated, low-privileged attacker to execute arbitrary code in the victim's browser via name field of a process.

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

## Which versions are affected by CVE-2022-39172?

It affects 1 product.


Products: Viva-Project Openviva.

## How do I fix CVE-2022-39172?

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

## Is CVE-2022-39172 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39172 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39172 and fix it if it is affected.

What it is: CVE-2022-39172 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39172 exists.

Affected product: n/a. 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-2022-39172/ (Markdown: https://insights.sbomify.com/CVE-2022-39172/index.md)
```

## Sources

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

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