dbcve.org
Cs31x FirmwareOperating system · Lexmark

CVE-2020-10094

MEDIUM · 5.4 CVSS v3.1 Published 2020-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A cross-site scripting (XSS) vulnerability in Lexmark CS31x before LW74.VYL.P273; CS41x before LW74.VY2.P273; CS51x before LW74.VY4.P273; CX310 before LW74.GM2.P273; CX410 & XC2130 before LW74.GM4.P273; CX510 & XC2132 before LW74.GM7.P273; MS310, MS312, MS317 before LW74.PRL.P273; MS410, M1140 before LW74.PRL.P273; MS315, MS415, MS417 before LW74.TL2.P273; MS51x, MS610dn, MS617 before LW74.PR2.P273; M1145, M3150dn before LW74.PR2.P273; MS610de, M3150 before LW74.PR4.P273; MS71x,M5163dn before LW74.DN2.P273; MS810, MS811, MS812, MS817, MS818 before LW74.DN2.P273; MS810de, M5155, M5163 before LW74.DN4.P273; MS812de, M5170 before LW74.DN7.P273; MS91x before LW74.SA.P273; MX31x, XM1135 before LW74.SB2.P273; MX410, MX510 & MX511 before LW74.SB4.P273; XM1140, XM1145 before LW74.SB4.P273; MX610 & MX611 before LW74.SB7.P273; XM3150 before LW74.SB7.P273; MX71x, MX81x before LW74.TU.P273; XM51xx & XM71xx before LW74.TU.P273; MX91x & XM91x before LW74.MG.P273; MX6500e before LW74.JD.P273; C746 before LHS60.CM2.P738; C748, CS748 before LHS60.CM4.P738; C792, CS796 before LHS60.HC.P738; C925 before LHS60.HV.P738; C950 before LHS60.TP.P738; X548 & XS548 before LHS60.VK.P738; X74x & XS748 before LHS60.NY.P738; X792 & XS79x before LHS60.MR.P738; X925 & XS925 before LHS60.HK.P738; X95x & XS95x before LHS60.TQ.P738; 6500e before LHS60.JR.P738;C734 LR.SK.P824 and earlier; C736 LR.SKE.P824 and earlier; E46x LR.LBH.P824 and earlier; T65x LR.JP.P824 and earlier; X46x LR.BS.P824 and earlier; X65x LR.MN.P824 and earlier; X73x LR.FL.P824 and earlier; W850 LP.JB.P823 and earlier; and X86x LP.SP.P823 and earlier.

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 confidence

A stored cross-site scripting (XSS) vulnerability exists in multiple Lexmark printer models. Attackers can inject malicious JavaScript into vulnerable input fields within the printer web interface. When authenticated users access affected pages, the injected script executes, potentially stealing session cookies or performing actions on behalf of the user.

MitigationUpdate Lexmark printer firmware to the patched versions specified in the advisory (LW74.xxxx.P273 or LHS60.xxxx.P738 or LR.xxxx.P824 or LP.xxxx.P823 depending on model series).

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
Cs31x FirmwareOperating system
Affected:<= lw74.vyl.p272
Cs41x FirmwareOperating system
Affected:<= lw74.vy2.p272
Cs51x FirmwareOperating system
Affected:<= lw74.vy4.p272
Cx310 FirmwareOperating system
Affected:<= lw74.gm2.p272
Cx410 FirmwareOperating system
Affected:<= lw74.gm4.p272
Xc2130 FirmwareOperating system
Affected:<= lw74.gm4.p272
Cx510 FirmwareOperating system
Affected:<= lw74.gm7.p272
Xc2132 FirmwareOperating system
Affected:<= lw74.gm7.p272

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Lexmark printer model
    Access the printer web interface and navigate to the 'About' or 'Device Status' page, or print a configuration/settings page from the printer control panel to locate the model name
    Affected if The model is one of: Cs31x, Cs41x, Cs51x, Cx310, Cx410, Xc2130, Cx510, or Xc2132
  2. Locate the firmware version
    In the printer web interface, go to 'Settings' > 'Device' > 'About' or 'Firmware', or check the printed configuration page for the firmware version string
    Affected if Unable to retrieve firmware version indicates limited visibility but does not confirm or rule out vulnerability
  3. Compare firmware version against affected thresholds
    Match the installed firmware version to the affected ranges: Cs31x <= lw74.vyl.p272, Cs41x <= lw74.vy2.p272, Cs51x <= lw74.vy4.p272, Cx310 <= lw74.gm2.p272, Cx410/Xc2130 <= lw74.gm4.p272, Cx510/Xc2132 <= lw74.gm7.p272
    Affected if The installed firmware version is at or below the specified version for that model series
  4. Verify web interface is accessible
    Attempt to reach the printer IP address over HTTP/HTTPS in a web browser. If the login page loads, the web interface is enabled
    Affected if Web interface is accessible and the firmware version meets the affected threshold criteria

A user is affected if their Lexmark printer model matches one of the eight listed models AND the installed firmware version is at or below the specific threshold for that model, with the printer web interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Lexmark printer firmware to the patched versions specified in the advisory (LW74.xxxx.P273 or LHS60.xxxx.P738 or LR.xxxx.P824 or LP.xxxx.P823 depending on model series).

Fix this in Cs31x Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-10094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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