CVE-2017-9292
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 · uneditedLansweeper before 6.0.0.65 has XSS in an image retrieval URI, aka Bug 542782.
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 confidenceCross-site scripting (XSS) vulnerability in Lansweeper's image retrieval URI in versions before 6.0.0.65 allows attackers to inject malicious script through crafted image requests. The vulnerability is exploitable remotely without authentication and requires user interaction (e.g., clicking a malicious link or viewing a compromised page).
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<= 6.0.0.64CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Locate the Lansweeper installationIdentify the server where Lansweeper is installed. The web application is typically hosted on IIS and accessible via a browser at the Lansweeper portal URL.Affected if Lansweeper is installed and accessible on the network
-
Check the installed Lansweeper versionLog into the Lansweeper web console as an administrator. Navigate to the Help section or About page where the version number is displayed. Alternatively, check the Lansweeper installation directory for a version file or check the Windows Programs and Features list.Affected if The displayed version is 6.0.0.64 or lower
-
Verify the image retrieval functionality is accessibleAccess the Lansweeper web interface and locate the image retrieval endpoint. This is typically found in areas where assets, scanning results, or user profile images are displayed. The vulnerable URI handles image requests.Affected if The web interface is accessible and the image retrieval feature is in use
-
Confirm the vulnerability conditionCompare your installed version against the affected range: versions 6.0.0.64 and below are vulnerable. The XSS exists specifically in the image retrieval URI where malicious script can be injected through crafted image requests.Affected if The installed version is 6.0.0.64 or any earlier 6.0.x version, and the image retrieval functionality is exposed via the web interface
You are affected if your Lansweeper installation is version 6.0.0.64 or earlier and the web-based image retrieval functionality is 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 dataUpdate Lansweeper to version 6.0.0.65 or later which contains the fix for this XSS vulnerability in the image retrieval functionality.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9292 — 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-2017-9292 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