CVE-2019-18791
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLexmark 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in the embedded web server of Lexmark MS812 and older generation printers allows attackers to inject malicious scripts that execute in authenticated users' browsers, enabling exfiltration of session credentials and other sensitive information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= lw73.vyl.p263<= lw73.vy2.p263<= lw73.gm2.p263<= lw73.prl.p263<= lw73.prl.p263<= lw73.prl.p263<= lw73.prl.p263<= lw73.prl.p263CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the printer modelCheck the product label on the device or access the embedded web server and look for the model number displayed on the login page or status pageAffected if Model is Lexmark Ms812 or older generation including Cx31x, Cx41x, Cx310, Ms310, Ms312, Ms317, Ms410, or M1140
-
Check firmware versionAccess the embedded web server, navigate to Settings or Status pages, and locate the firmware version information. Compare against affected version ranges: Cx31x <= lw73.vyl.p263, Cx41x <= lw73.vy2.p263, Cx310 <= lw73.gm2.p263, Ms310/Ms312/Ms317/Ms410/M1140 <= lw73.prl.p263Affected if Firmware version is at or below the specified threshold for your model
-
Verify embedded web server is enabledAccess the printer control panel or embedded web server and check the web services or network configuration settings to confirm the HTTP/HTTPS web server is activeAffected if Embedded web server is running and accessible
-
Confirm remote web management accessCheck network settings to determine if the web interface is accessible remotely (not just from direct-connected hosts). Look for HTTP/HTTPS listening on external interfaces or WAN-facing IP addressesAffected if Web interface is accessible from network segments beyond trusted local networks
You are affected if your Lexmark printer model matches one of the listed models and your firmware version is at or below the specified threshold while the embedded web server is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied firmware updates when available; alternatively, restrict web interface access to trusted networks or disable remote web management if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-18791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-18791 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data