CVE-2017-12460
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 · uneditedAn issue was discovered in Barco ClickShare CSM-1 firmware before v1.7.0.3 and CSC-1 firmware before v1.10.0.10. An authenticated user can manage the wallpaper collection in the webUI to be shown as background on the ClickShare product. By uploading a wallpaper with a specially crafted name, an HTML injection can be triggered as special characters are not neutralized before output.
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 confidenceHTML injection vulnerability in Barco ClickShare CSM-1 (before v1.7.0.3) and CSC-1 (before v1.10.0.10) firmware. An authenticated user can upload a wallpaper with a specially crafted name containing HTML special characters that are not sanitized before output in the webUI, allowing HTML injection.
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< 1.7.0.3< 1.10.0.10CVSS 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.0/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 ClickShare modelLog into the ClickShare web interface and locate the device information or system status page to determine if the unit is a CSM-1 or CSC-1 model.Affected if The device is a Barco ClickShare CSM-1 or CSC-1 unit.
-
Check the installed firmware versionIn the web interface, navigate to the About or System Information section and note the firmware version number displayed.Affected if The firmware version is below 1.7.0.3 for CSM-1 units, or below 1.10.0.10 for CSC-1 units.
-
Verify wallpaper upload feature availabilityNavigate to the Admin or Settings area of the web interface and look for a Wallpaper, Custom Background, or Branding settings section where image uploads can be performed.Affected if The wallpaper upload feature is present and accessible in the web interface.
-
Confirm authentication access to the featureDetermine if standard users (non-administrators) have access to the wallpaper upload functionality by checking user role permissions or attempting to access with a regular user account.Affected if Standard users or any authenticated user can access the wallpaper upload feature.
A user is affected if they are running a vulnerable CSM-1 firmware below v1.7.0.3 or CSC-1 firmware below v1.10.0.10, and the wallpaper upload feature is accessible to authenticated users on their 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 data1.7.0.31.10.0.10
Upgrade firmware to v1.7.0.3 (CSM-1) or v1.10.0.10 (CSC-1) or later. If upgrade is not immediately feasible, restrict administrative access to the wallpaper management feature and implement network segmentation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12460 — 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-12460 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