# CVE-2023-40239: XML external entity in n/a

> Attackers can exploit an XML External Entity vulnerability in Lexmark printer firmware to disclose sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2023
- **Updated:** 1 Oct 2024
- **Also known as:** GHSA-cwqw-75wv-wxpm

## What is CVE-2023-40239?

CVE-2023-40239 is a high-severity vulnerability in n/a, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain Lexmark devices (such as CS310) before 2023-08-25 allow XXE attacks, leading to information disclosure. The fixed firmware version is LW80.*.P246, i.e., '*' indicates that the full version specification varies across product model family, but firmware level P246 (or higher) is required to remediate the vulnerability.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 82 products.


Products: Lexmark C2132 Firmware, Lexmark Cs310 Firmware, Lexmark Cs317 Firmware, Lexmark Cs410 Firmware, Lexmark Cs417 Firmware, Lexmark Cs510 Firmware, Lexmark Cs517 Firmware, Lexmark Cx310 Firmware, Lexmark Cx317 Firmware, Lexmark Cx410 Firmware, Lexmark Cx417 Firmware, Lexmark Cx510 Firmware, Lexmark Cx517 Firmware, Lexmark M1140\+ Firmware, Lexmark M1140 Firmware, Lexmark M1145 Firmware, Lexmark M3150de Firmware, Lexmark M3150dn Firmware, Lexmark M5155 Firmware, Lexmark M5163de Firmware and 62 more.

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

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

## Is CVE-2023-40239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-40239 is a high-severity vulnerability in n/a, published on 1 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-40239 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-2023-40239/ (Markdown: https://insights.sbomify.com/CVE-2023-40239/index.md)
```

## Sources

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

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