Skip to content
Noroxi
CVE-2019-18791· NVD / CVE Program· CNA mitre

Lexmark printer MS812 and multiple older generation Lexmark devices have a stored XSS vulnerability in the embedded web server.

Lexmark printer MS812 and multiple older generation Lexmark devices have a stored XSS vulnerability in the embedded web server. The vulnerability can be exploited to expose session credentials and other information via the users web browser.

MediumCVSS 5.4 · v3.1—No exploit No fix recorded
Published
Feb 13, 2020
Updated
Jun 16, 2026
EPSS
0.5% · 43th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

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 help

Affected systems

VendorProduct
lexmarkcx31x firmware
lexmarkcx31x
lexmarkcx41x firmware
lexmarkcx41x
lexmarkcx310 firmware
lexmarkcx310
lexmarkms310 firmware
lexmarkms310
lexmarkms312 firmware
lexmarkms312
lexmarkms317 firmware
lexmarkms317

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.p731 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.p731 inclusive
  • lexmark c792 firmwareup to lhs60.hc.p731 inclusive
  • lexmark c925 firmwareup to lhs60.hv.p731 inclusive
  • lexmark c950 firmwareup to lhs60.tp.p731 inclusive
  • lexmark cs748 firmwareup to lhs60.cm4.p731 inclusive
  • lexmark cs796 firmwareup to lhs60.hc.p731 inclusive
  • lexmark cx310 firmwareup to lw73.gm2.p263 inclusive
  • lexmark cx31x firmwareup to lw73.vyl.p263 inclusive
  • lexmark cx410 firmwareup to lw73.gm4.p263 inclusive
  • lexmark cx41x firmwareup to lw73.vy2.p263 inclusive
  • lexmark cx510 firmwareup to lw73.gm7.p263 inclusive
  • lexmark cx51x firmwareup to lw73.vy4.p263 inclusive
  • lexmark e46x firmwareup to lr.lbh.p822 inclusive
  • lexmark m1140 firmwareup to lw73.prl.p263 inclusive
  • lexmark m1145 firmwareup to lw73.pr2.p263 inclusive
  • lexmark m3150 firmwareup to lw73.pr4.p263 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.

EPSS, last 120 days

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.

Finders, 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.
  • 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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
commentEl.innerHTML = comment.body;

Fixed

ts
commentEl.textContent = comment.body;

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

All records