CVE-2018-6842
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 · uneditedKentico 10 before 10.0.50 and 11 before 11.0.3 has XSS in which a crafted URL results in improper construction of a system page.
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 Kentico CMS versions 10 before 10.0.50 and 11 before 11.0.3 allows attackers to inject malicious scripts via crafted URLs that improperly construct system pages.
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>= 10.0, < 10.0.50>= 11.0, < 11.0.3CVSS 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 installed Kentico versionLog into the Kentico CMS administration panel and navigate to the 'About' section, or check the version in the CMS Desk > Help > About. Alternatively, inspect the DLL files in the /bin directory (particularly CMS.dll) for the version number, or query the CMS_SettingsKey table in the database for 'CMSVersion' key.Affected if The installed version falls within 10.0.0 to 10.0.49, or 11.0.0 to 11.0.2 (any version below 10.0.50 or 11.0.3).
-
Verify URL rewriting is enabledOpen the web.config file in the Kentico installation root and look for the 'URLRewriting' or 'URL Rewrite' settings in the <appSettings> or <modules> section. Also check in Kentico administration under Settings > URL Formatting > Friendly URLs.Affected if URL rewriting/friendly URLs are enabled on a vulnerable version.
-
Check for system page handlersInspect the ~/CMSModules/ or ~/CMSPages/ directories for .aspx files that handle system page rendering. In particular, examine files like error pages, redirection handlers, or virtual URL handlers that process incoming request paths.Affected if The system uses built-in Kentico page handlers that construct URLs from request parameters.
-
Review URL request logs for XSS patternsExamine IIS log files (W3C Extended Log Format) in the C:\inetpub\logs\LogFiles directory (or equivalent) for the W3SVC site. Search for URL patterns containing script tags, javascript:, or HTML tags in query string parameters.Affected if Logs show requests with malicious script injection patterns in URLs that were processed by Kentico pages.
The environment is affected if the installed Kentico version is 10.0.0 through 10.0.49, or 11.0.0 through 11.0.2, and URL-related features are enabled.
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 data10.0.5011.0.3
Upgrade to Kentico 10.0.50, 11.0.3, or later to patch the XSS vulnerability.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6842 — 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-2018-6842 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