CVE intelligence and bounded remediation
CVE-2019-6332 — A potential security vulnerability has been identified with certain HP InkJet printers
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…
- Severity
- Medium
- CVSS
- 4.8 (3.1)
- Published
- 2020-01-09
- CISA KEV
- Not currently listed
- Ecosystem
- operating-system
- Weaknesses
- CWE-79
Affected 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
Matched remediation archetype
Cross-site scripting and unsafe browser output
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
- Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
- Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.
Remediate safely
- Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
- Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
- Update affected rendering components and add tests for every output context using inert sentinel markup.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.