dbcve.org
Telerik ReportingApplication · Progress

CVE-2017-9140

MEDIUM · 6.1 CVSS v3.0 Published 2017-05-22
Fix available
A fix is available. Upgrade to 11.0.17.406 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting (XSS) vulnerability in Telerik.ReportViewer.WebForms.dll in Telerik Reporting for ASP.NET WebForms Report Viewer control before R1 2017 SP2 (11.0.17.406) allows remote attackers to inject arbitrary web script or HTML via the bgColor parameter to Telerik.ReportViewer.axd.

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

Cross-site scripting (XSS) vulnerability in the Telerik Reporting WebForms Report Viewer control allows remote attackers to inject arbitrary web script or HTML via the bgColor parameter in the Telerik.ReportViewer.axd endpoint. The vulnerability exists in versions before R1 2017 SP2 (11.0.17.406).

MitigationUpgrade Telerik Reporting to version R1 2017 SP2 (11.0.17.406) or later. If immediate upgrade is not possible, implement input validation and output encoding on the bgColor parameter as a compensating control.

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
Telerik ReportingApplication
Affected:< 11.0.17.406
Sitefinity CmsApplication
Affected:>= 4.2, <= 11.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Telerik Reporting version
    Check the installed Telerik Reporting version by inspecting the Telerik.Reporting.dll file properties in the bin folder, or query the assembly version via PowerShell: [System.Diagnostics.FileVersionInfo]::GetVersionInfo('path\to\Telerik.Reporting.dll').FileVersion
    Affected if Version is below 11.0.17.406 (R1 2017 SP2)
  2. Identify Sitefinity CMS version
    If using Sitefinity CMS, check its version in the bin folder assembly or Sitefinity configuration. Telerik Reporting is bundled with Sitefinity versions 4.2 through 11.0
    Affected if Sitefinity version is between 4.2 and 11.0 inclusive
  3. Verify WebForms Report Viewer is in use
    Search the application codebase for references to Telerik.ReportViewer.WebForms.ReportViewer control in .aspx or .ascx files, or check web.config for ReportViewer handler registrations
    Affected if The WebForms Report Viewer control (Telerik.ReportViewer.WebForms.ReportViewer) is present in the application
  4. Check Telerik.ReportViewer.axd endpoint accessibility
    Attempt to access the Telerik.ReportViewer.axd endpoint directly in a browser or via curl: http://yourdomain/Telerik.ReportViewer.axd?bgColor=test
    Affected if The endpoint responds and accepts the bgColor parameter without sanitization
  5. Inspect HTTP response for XSS vulnerability
    Send a crafted bgColor parameter with XSS payload (e.g., bgColor=%3Cscript%3Ealert(1)%3C/script%3E) and verify if the value is reflected unsanitized in the response
    Affected if The bgColor parameter value is reflected in the HTML response without encoding or validation

The environment is affected if Telerik Reporting version is below 11.0.17.406 OR Sitefinity CMS versions 4.2-11.0 are in use AND the WebForms Report Viewer with Telerik.ReportViewer.axd endpoint is accessible.

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 11.0.17.406 or later
Fixed in 11.0.17.406
Interim mitigation

Upgrade Telerik Reporting to version R1 2017 SP2 (11.0.17.406) or later. If immediate upgrade is not possible, implement input validation and output encoding on the bgColor parameter as a compensating control.

Fix this in Telerik Reporting Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-9140 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