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

> Stored XSS in Lexmark printer web servers allows attackers to steal session credentials and sensitive information from users.

- **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:** 13 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4v8q-wq3r-x874

## What is CVE-2019-18791?

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

### Official description

Lexmark printer MS812 and multiple older generation Lexmark devices have a stored XSS vulnerability in the embedded web server. The vulnerability can be exploited to expose session credentials and other information via the users web browser.

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

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

It affects 80 products.


Products: Lexmark 6500e Firmware, Lexmark C734 Firmware, Lexmark C736 Firmware, Lexmark C746 Firmware, Lexmark C748 Firmware, Lexmark C792 Firmware, Lexmark C925 Firmware, Lexmark C950 Firmware, Lexmark Cs748 Firmware, Lexmark Cs796 Firmware, Lexmark Cx310 Firmware, Lexmark Cx31x Firmware, Lexmark Cx410 Firmware, Lexmark Cx41x Firmware, Lexmark Cx510 Firmware, Lexmark Cx51x Firmware, Lexmark E46x Firmware, Lexmark M1140 Firmware, Lexmark M1145 Firmware, Lexmark M3150 Firmware and 60 more.

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

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

## Is CVE-2019-18791 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-44734](https://insights.sbomify.com/CVE-2021-44734/): Code injection in n/a (critical 9.8)
- [CVE-2021-44738](https://insights.sbomify.com/CVE-2021-44738/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9930](https://insights.sbomify.com/CVE-2019-9930/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-9932](https://insights.sbomify.com/CVE-2019-9932/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-9933](https://insights.sbomify.com/CVE-2019-9933/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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