# CVE-2026-71803: Cross-site scripting in n/a

> Attackers with product creation privileges can inject malicious scripts into order logs, leading to code execution when administrators view them.

- **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:** 9 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-8r46-2jjc-h8fg

## What is CVE-2026-71803?

CVE-2026-71803 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 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

money-pos 1.0 contains a stored Cross-Site Scripting (XSS) vulnerability. When processing returns, the backend fails to filter or escape the goodsName parameter, directly concatenating it into the order log description; the frontend subsequently renders this content using v-html. An attacker with product creation privileges can inject a malicious JavaScript payload, causing unauthorized code execution when an administrator views the order logs.

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

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


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

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

## Is CVE-2026-71803 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71803 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Sep 2026. 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-2026-71803 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-2026-71803/ (Markdown: https://insights.sbomify.com/CVE-2026-71803/index.md)
```

## Sources

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

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