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

> Persistent XSS in XMPie UStore admin panel allows attackers to inject scripts via user editing fields, potentially compromising administrator accounts.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Feb 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-xxpf-rq7v-q2rc

## What is CVE-2022-23321?

CVE-2022-23321 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A persistent cross-site scripting (XSS) vulnerability exists on two input fields within the administrative panel when editing users in the XMPie UStore application on version 12.3.7244.0.

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

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

It affects 1 product.


Products: Xerox Xmpie Ustore.

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

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

## Is CVE-2022-23321 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-23320](https://insights.sbomify.com/CVE-2022-23320/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23321 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Feb 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23321 in the wild and no public exploit code.

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-23321/ (Markdown: https://insights.sbomify.com/CVE-2022-23321/index.md)
```

## Sources

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

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