# CVE-2023-1526: Information disclosure in HP DesignJet and PageWide XL

> Attackers with physical access can extract data from removed hard drives in certain HP DesignJet and PageWide XL printers.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2023
- **Updated:** 30 Jan 2025
- **Also known as:** GHSA-vr7w-hjq6-6hc3

## What is CVE-2023-1526?

CVE-2023-1526 is a medium-severity vulnerability in HP DesignJet and PageWide XL, published on 28 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Certain DesignJet and PageWide XL TAA compliant models may have risk of potential information disclosure if the hard disk drive is physically removed from the printer.

## Which versions are affected by CVE-2023-1526?

It affects 10 products.


Products: Hp Designjet Z6 Firmware, Hp Designjet Z6dr Firmware, Hp Designjet Z9\+ Pro Firmware, Hp Designjet Z9 Firmware, Hp Designjet Z9dr Firmware, Hp Pagewide Xl 4100, Hp Pagewide Xl 4500, Hp Pagewide Xl 4600, Hp Pagewide Xl 4700, Hp Pagewide Xl 8000.

## How do I fix CVE-2023-1526?

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

## Is CVE-2023-1526 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1526 and fix it if it is affected.

What it is: CVE-2023-1526 is a medium-severity vulnerability in HP DesignJet and PageWide XL, published on 28 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1526 in the wild and no public exploit code.

Affected product: HP DesignJet and PageWide XL. 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-2023-1526/ (Markdown: https://insights.sbomify.com/CVE-2023-1526/index.md)
```

## Sources

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

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