Certain Lexmark devices (such as CS310) before 2023-08-25 allow XXE attacks, leading to information disclosure.
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.
- Published
- Sep 1, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.5% · 43th percentile
- CWE
- CWE-611
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| lexmark | c2132 firmware | cpe:2.3:o:lexmark:c2132_firmware |
| lexmark | c2132 | cpe:2.3:h:lexmark:c2132 |
| lexmark | cs310 firmware | cpe:2.3:o:lexmark:cs310_firmware |
| lexmark | cs310 | cpe:2.3:h:lexmark:cs310 |
| lexmark | cs317 firmware | cpe:2.3:o:lexmark:cs317_firmware |
| lexmark | cs317 | cpe:2.3:h:lexmark:cs317 |
| lexmark | cs410 firmware | cpe:2.3:o:lexmark:cs410_firmware |
| lexmark | cs410 | cpe:2.3:h:lexmark:cs410 |
| lexmark | cs417 firmware | cpe:2.3:o:lexmark:cs417_firmware |
| lexmark | cs417 | cpe:2.3:h:lexmark:cs417 |
| lexmark | cs510 firmware | cpe:2.3:o:lexmark:cs510_firmware |
| lexmark | cs510 | cpe:2.3:h:lexmark:cs510 |
and 152 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lexmark c2132 firmwareup to lw80.vy4.p245 inclusive
- lexmark cs310 firmwareup to lw80.vyl.p245 inclusive
- lexmark cs317 firmwareup to lw80.vyl.p245 inclusive
- lexmark cs410 firmwareup to lw80.vy2.p245 inclusive
- lexmark cs417 firmwareup to lw80.vy2.p245 inclusive
- lexmark cs510 firmwareup to lw80.vy4.p245 inclusive
- lexmark cs517 firmwareup to lw80.vy4.p245 inclusive
- lexmark cx310 firmwareup to lw80.gm2.p245 inclusive
- lexmark cx317 firmwareup to lw80.gm2.p245 inclusive
- lexmark cx410 firmwareup to lw80.gm4.p245 inclusive
- lexmark cx417 firmwareup to lw80.gm4.p245 inclusive
- lexmark cx510 firmwareup to lw80.gm7.p245 inclusive
- lexmark cx517 firmwareup to lw80.gm7.p245 inclusive
- lexmark m1140 firmwareup to lw80.prl.p245 inclusive
- lexmark m1140+ firmwareup to lw80.pr2.p245 inclusive
- lexmark m1145 firmwareup to lw80.pr2.p245 inclusive
- lexmark m3150de firmwareup to lw80.pr4.p245 inclusive
- lexmark m3150dn firmwareup to lw80.pr2.p245 inclusive
- lexmark m5155 firmwareup to lw80.dn4.p245 inclusive
- lexmark m5163de firmwareup to lw80.dn4.p245 inclusive
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-611 · Improper Restriction of XML External Entity ReferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.