# CVE-2019-6332: Cross-site scripting in HP DeskJet 2600 All-in-One Printer series

> Cross-site scripting vulnerability in HP InkJet printers allows attackers to inject malicious scripts, potentially compromising user sessions or data.

- **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:** 9 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p36j-vcf6-4h58

## What is CVE-2019-6332?

CVE-2019-6332 is a medium-severity cross-site scripting vulnerability in HP DeskJet 2600 All-in-One Printer series, published on 9 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A potential security vulnerability has been identified with certain HP InkJet printers. The vulnerability could be exploited to allow cross-site scripting (XSS). Affected products and versions include: HP DeskJet 2600 All-in-One Printer series model numbers 4UJ28B, V1N01A - V1N08A, Y5H60A - Y5H80A; HP DeskJet Ink Advantage 2600 All-in-One Printer series model numbers V1N02A - V1N02B, Y5Z00A - Y5Z04B; HP DeskJet Ink Advantage 5000 All-in-One Printer series model numbers M2U86A - M2U89B; HP DeskJet Ink Advantage 5200 All-in-One Printer series model numbers M2U76A - M2U78B; HP ENVY 5000 All-in-One Printer series model numbers M2U85A - M2U85B, M2U91A - M2U94B, Z4A54A - Z4A74A; HP ENVY Photo 6200 All-in-One Printer series model numbers K7G18A-K7G26B, K7S21B, Y0K13D - Y0K15A; HP ENVY Photo 7100 All-in-One Printer series model numbers 3XD89A, K7G93A-K7G99A, Z3M37A - Z3M52A; HP ENVY Photo 7800 All-in-One Printer series model numbers K7R96A, K7S00A - K7S10D, Y0G42D - Y0G52B; HP Ink Tank Wireless 410 series model numbers Z4B53A - Z4B55A, Z6Z95A - Z6Z99A, 4DX94A - 4DX95A, 4YF79A, Z7A01A; HP OfficeJet 5200 All-in-One Printer series model numbers M2U75A, M2U81A-M2U84B, Z4B12A - Z4B14A, Z4B27A - Z4B29A; HP Smart Tank Wireless 450 series model numbers Z4B56A, Z6Z96A - Z6Z98A.

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

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

It affects 52 products.


Products: Hp Deskjet 2600 4uj28b Firmware, Hp Deskjet 2600 V1n01a Firmware, Hp Deskjet 2600 V1n08a Firmware, Hp Deskjet 2600 Y5h60a Firmware, Hp Deskjet 2600 Y5h80a Firmware, Hp Deskjet Ink Advantage 2600 V1n02a Firmware, Hp Deskjet Ink Advantage 2600 V1n02b Firmware, Hp Deskjet Ink Advantage 2600 Y5z00a Firmware, Hp Deskjet Ink Advantage 2600 Y5z04b Firmware, Hp Deskjet Ink Advantage 5000 M2u86a Firmware, Hp Deskjet Ink Advantage 5000 M2u89b Firmware, Hp Deskjet Ink Advantage 5200 M2u76a Firmware, Hp Deskjet Ink Advantage 5200 M2u78b Firmware, Hp Envy 5000 M2u85a Firmware, Hp Envy 5000 M2u85b Firmware, Hp Envy 5000 M2u91a Firmware, Hp Envy 5000 M2u94b Firmware, Hp Envy 5000 Z4a54a Firmware, Hp Envy 5000 Z4a74a Firmware, Hp Envy Photo 6200 K7g18a Firmware and 32 more.

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

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

## Is CVE-2019-6332 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6332 is a medium-severity cross-site scripting vulnerability in HP DeskJet 2600 All-in-One Printer series, published on 9 Jan 2020. 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-2019-6332 in the wild and no public exploit code.

Affected product: HP DeskJet 2600 All-in-One Printer series. 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-6332/ (Markdown: https://insights.sbomify.com/CVE-2019-6332/index.md)
```

## Sources

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

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