CVE-2016-6133
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 · uneditedCross-site scripting (XSS) vulnerability in Ektron Content Management System before 9.1.0.184SP3(9.1.0.184.3.127) allows remote attackers to inject arbitrary web script or HTML via the rptStatus parameter in a Report action to WorkArea/SelectUserGroup.aspx.
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 confidenceReflected XSS vulnerability in Ektron CMS WorkArea/SelectUserGroup.aspx where the rptStatus parameter in a Report action is not properly sanitized, allowing injection of arbitrary JavaScript/HTML that executes in victim 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<= 9.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
- 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.
-
Identify installed Ektron CMS versionLocate the version information in the Ektron CMS installation. Typically found in the CMS400Web/bin folder as version info, or check the siteproperties.config, version.config, or AssemblyInfo files within the Ektron installation directory.Affected if The installed version is 9.10 or any version lower than 9.10 (e.g., 9.0, 8.x, etc.)
-
Confirm affected endpoint existsCheck if the file WorkArea/SelectUserGroup.aspx exists in the web application's directory structure. This is typically located under /WorkArea/SelectUserGroup.aspx within the Ektron CMS web root.Affected if The file exists and is accessible via the web server
-
Verify rptStatus parameter is processedReview the application's handling of the rptStatus parameter in SelectUserGroup.aspx or its code-behind. Check if the Report functionality that uses this parameter is enabled or accessible in the WorkArea.Affected if The rptStatus parameter is accepted and reflected in the response without sanitization, which can only be confirmed by code review or controlled testing
-
Confirm CMS is accessible over networkVerify the Ektron CMS WorkArea interface is reachable. Attempt to access the WorkArea login or the SelectUserGroup.aspx page via HTTP/HTTPS to confirm the application is exposed.Affected if The WorkArea is accessible, meaning potential attackers could trigger the XSS via crafted URLs
A user is affected if they are running Ektron CMS version 9.10 or lower and have the WorkArea/SelectUserGroup.aspx page accessible with the rptStatus parameter vulnerable to injection.
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 dataUpgrade to Ektron CMS version 9.1.0.184SP3 (9.1.0.184.3.127) or later. Alternatively, implement input validation and output encoding on the rptStatus parameter to neutralize malicious script injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6133 — 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-2016-6133 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