Xclarity AdministratorApplication · Lenovo

CVE-2019-19757

MEDIUM · 5.4 CVSS v3.1 Published 2020-02-14
Fix available
A fix is available. Upgrade to 2.6.6 or later.
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
An internal product security audit of Lenovo XClarity Administrator (LXCA) discovered a Document Object Model (DOM) based cross-site scripting vulnerability in versions prior to 2.6.6 that could allow JavaScript code to be executed in the user's web browser if a specially crafted link is visited. The JavaScript code is executed on the user's system, not executed on LXCA itself.

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

DOM-based cross-site scripting (XSS) vulnerability in Lenovo XClarity Administrator (LXCA) versions prior to 2.6.6. The vulnerability exists in client-side code where user-supplied input is improperly handled when manipulating the Document Object Model (DOM), allowing execution of arbitrary JavaScript in a user's browser when they visit a specially crafted link.

MitigationUpgrade Lenovo XClarity Administrator to version 2.6.6 or later. Users should be advised to avoid clicking untrusted links as a defense-in-depth measure.

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
Xclarity AdministratorApplication
Affected:< 2.6.6

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. Verify Lenovo XClarity Administrator is running
    Access the LXCA web interface via its URL (typically https://<server>/lcma) or check if the service process is running on the host
    Affected if LXCA is accessible and running
  2. Identify the installed LXCA version
    Log into the LXCA web interface and navigate to the About or System Information page to view the version number, or use the command-line interface if available
    Affected if Unable to determine version or version is displayed
  3. Compare version against affected range
    Check if the installed version is less than 2.6.6 - the affected versions are any release prior to 2.6.6
    Affected if Version number is below 2.6.6 (for example, 2.6.5, 2.5.0, 2.4.0, etc.)

You are affected if Lenovo XClarity Administrator is running and the installed version is any release prior to 2.6.6.

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
Upgrade available Upgrade to 2.6.6 or later
Fixed in 2.6.6
Interim mitigation

Upgrade Lenovo XClarity Administrator to version 2.6.6 or later. Users should be advised to avoid clicking untrusted links as a defense-in-depth measure.

Fix this in Xclarity Administrator Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19757 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-19757 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