# CVE-2026-18243: HP DesignJet T3500 - Potential Cross-Site Scripting (XSS)

> Unauthenticated attackers can exploit XSS to view print job previews on HP DesignJet T3500 printers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-fvf7-w3m5-7r54

## What is CVE-2026-18243?

CVE-2026-18243 is a medium-severity cross-site scripting vulnerability in HP DesignJet T3500, published on 3 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Certain HP DesignJet products may be potentially vulnerable to cross-site scripting (XSS), which may allow unauthenticated HTTP requests to view print job previews.

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

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


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

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

## Is CVE-2026-18243 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18243 is a medium-severity cross-site scripting vulnerability in HP DesignJet T3500, published on 3 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-18243 in the wild and no public exploit code.

Affected product: HP DesignJet T3500. 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-18243/ (Markdown: https://insights.sbomify.com/CVE-2026-18243/index.md)
```

## Sources

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

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