Various Lexmark products have reflected XSS in the embedded web server used in older generation Lexmark devices.
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Various Lexmark products have reflected XSS in the embedded web server used in older generation Lexmark devices. Affected products are available in http://support.lexmark.com/index?page=content&id=TE935&locale=en&userlocale=EN_US.
- Published
- Mar 6, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.7% · 50th percentile
- CWE
- CWE-79
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| lexmark | cs31x firmware | cpe:2.3:o:lexmark:cs31x_firmware |
| lexmark | cs31x | cpe:2.3:h:lexmark:cs31x |
| lexmark | cs41x firmware | cpe:2.3:o:lexmark:cs41x_firmware |
| lexmark | cs41x | cpe:2.3:h:lexmark:cs41x |
| lexmark | cs51x firmware | cpe:2.3:o:lexmark:cs51x_firmware |
| lexmark | cs51x | cpe:2.3:h:lexmark:cs51x |
| lexmark | cx310 firmware | cpe:2.3:o:lexmark:cx310_firmware |
| lexmark | cx310 | cpe:2.3:h:lexmark:cx310 |
| lexmark | cx410 firmware | cpe:2.3:o:lexmark:cx410_firmware |
| lexmark | cx410 | cpe:2.3:h:lexmark:cx410 |
| lexmark | xc2130 firmware | cpe:2.3:o:lexmark:xc2130_firmware |
| lexmark | xc2130 | cpe:2.3:h:lexmark:xc2130 |
and 148 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lexmark 6500e firmwareup to lhs60.jr.p735 inclusive
- lexmark c734 firmwareup to lr.sk.p822 inclusive
- lexmark c736 firmwareup to lr.ske.p822 inclusive
- lexmark c746 firmwareup to lhs60.cm2.p731 inclusive
- lexmark c748 firmwareup to lhs60.cm4.p735 inclusive
- lexmark c792 firmwareup to lhs60.hc.p735 inclusive
- lexmark c925 firmwareup to lhs60.hv.p735 inclusive
- lexmark c950 firmwareup to lhs60.tp.p735 inclusive
- lexmark cs31x firmwareup to lw74.vyl.p267 inclusive
- lexmark cs41x firmwareup to lw74.vy2.p267 inclusive
- lexmark cs51x firmwareup to lw74.vy4.p267 inclusive
- lexmark cs748 firmwareup to lhs60.cm4.p735 inclusive
- lexmark cs796 firmwareup to lhs60.hc.p735 inclusive
- lexmark cx310 firmwareup to lw74.gm2.p267 inclusive
- lexmark cx410 firmwareup to lw74.gm4.p267 inclusive
- lexmark cx510 firmwareup to lw74.gm7.p267 inclusive
- lexmark e46x firmwareup to lr.lbh.p822 inclusive
- lexmark m1140 firmwareup to lw74.prl.p267 inclusive
- lexmark m1145 firmwareup to lw74.pr2.p267 inclusive
- lexmark m3150 firmwareup to lw74.pr4.p267 inclusive
Same product
lexmark: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-9933Various Lexmark products have a Buffer Overflow (issue 3 of 3).39Monitor
- CVE-2019-9932Various Lexmark products have a Buffer Overflow (issue 2 of 3).39Monitor
- CVE-2019-9930Various Lexmark products have an Integer Overflow.39Monitor
- CVE-2019-10058Various Lexmark products have Incorrect Access Control.36Monitor
- CVE-2019-9931Various Lexmark printers contain a denial of service vulnerability in the SNMP service that can be exploited to crash the device.30Monitor
- CVE-2019-10057Various Lexmark products have CSRF.26Monitor
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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-139 · Mar 10, 2020(Lexmark Yazıcı Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;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.