CVE-2019-19772
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 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.
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 confidenceReflected cross-site scripting (XSS) vulnerability in the embedded web server of older generation Lexmark devices. User-supplied input is rendered in HTTP responses without proper sanitization, allowing attackers to inject malicious scripts that execute in the context of authenticated users' browsers.
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 web interface and check the home page or status page, or print a configuration page from the device control panel to locate the model name (such as Cs31x, Cs41x, Cx310, etc.)Affected if The device model matches one of the affected models: Cs31x, Cs41x, Cs51x, Cx310, Cx410, Xc2130, Cx510, or Xc2132
-
Determine the installed firmware versionIn the device web interface, navigate to Settings or Status pages and locate the firmware version field. It will appear as a version string such as lw74.vyl.p267 or similar.Affected if The firmware version is at or below the threshold for your model: lw74.vyl.p267 (Cs31x), lw74.vy2.p267 (Cs41x), lw74.vy4.p267 (Cs51x), lw74.gm2.p267 (Cx310), lw74.gm4.p267 (Cx410/Xc2130), or lw74.gm7.p267 (Cx510/Xc2132)
-
Confirm the embedded web server is enabledAccess the device web interface on the standard HTTP/HTTPS ports (typically 80/443) or check in the device Settings under Network/Ports to verify the embedded web server (Web Server or HTTP Server) is turned on.Affected if The web management interface is accessible over HTTP/HTTPS, as the XSS payload is delivered through HTTP responses from this server
-
Verify the device is reachable on the networkPing the device IP address or attempt to connect to the web interface URL (http://[device-ip] or https://[device-ip]) to confirm network accessibility.Affected if The device management interface is network-accessible, which is required for an attacker to inject the malicious XSS payload into an authenticated user's browser
You are affected if your Lexmark device model is one of the listed models AND your firmware version is at or below the specified threshold AND the embedded web server interface is accessible on the network.
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 dataUpdate affected Lexmark devices to the latest firmware version provided by Lexmark support. If updates are unavailable, implement web application firewall (WAF) rules or network segmentation to limit exposure to the device management interface.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19772 — 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-19772 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