# CVE-2019-16330: Cross-site scripting in n/a

> An authenticated user can inject arbitrary JavaScript into accounting fields, potentially executing code or modifying data in NCH Express Accounts.

- **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:** 17 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-95j3-4qj7-3qrm

## What is CVE-2019-16330?

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

### Official description

In NCH Express Accounts Accounting v7.02, persistent cross site scripting (XSS) exists in Invoices/Sales Orders/Items/Customers/Quotes input field. An authenticated unprivileged user can add/modify the Invoices/Sales Orders/Items/Customers/Quotes fields parameter to inject arbitrary JavaScript.

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

## Which versions are affected by CVE-2019-16330?

It affects 1 product.


Products: Nchsoftware Express Accounts Accounting.

## How do I fix CVE-2019-16330?

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

## Is CVE-2019-16330 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16330 and fix it if it is affected.

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

## Sources

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

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