CVE-2019-19773
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 · uneditedVarious Lexmark products have stored 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.
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in the embedded web server of older generation Lexmark devices. The malicious script is persisted on the device and executes when users access affected pages, potentially allowing session hijacking or credential theft.
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<= lw74.vyl.p267<= lw74.vy2.p267<= lw74.vy4.p267<= lw74.gm2.p267<= lw74.gm4.p267<= lw74.gm4.p267<= lw74.gm7.p267<= lw74.gm7.p267CVSS 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 Lexmark device modelAccess the device's web interface or print a configuration page to confirm the exact model number (Cs31x, Cs41x, Cs51x, Cx310, Cx410, Xc2130, Cx510, or Xc2132)Affected if The device model is NOT one of these eight models - the vulnerability does not apply
-
Check the installed firmware versionIn the web interface, navigate to Settings > General Setup > About, or print a configuration page to locate the firmware version stringAffected if The firmware version is at or below lw74.vyl.p267 (Cs31x), lw74.vy2.p267 (Cs41x), lw74.vy4.p267 (Cs51x/Cx410/Xc2130), lw74.gm2.p267 (Cx310), or lw74.gm7.p267 (Cx510/Xc2132)
-
Confirm the embedded web server is enabledIn the web interface, verify that HTTP/HTTPS management access is available under Settings > General Setup > Network/Ports, or check if TCP port 80 or 443 is respondingAffected if The web server is disabled and not accessible - the attack surface is not present; however, if it is enabled, the stored XSS could trigger for users accessing the interface
Your device is affected if it is a Lexmark Cs31x, Cs41x, Cs51x, Cx310, Cx410, Xc2130, Cx510, or Xc2132 with firmware at or below the version thresholds AND the embedded web management interface is enabled.
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 available firmware updates from Lexmark's support portal (refer to TE935). If updates are unavailable, consider network isolating affected devices or disabling the web management interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19773 — 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-19773 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