CVE-2018-6843
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 SQL injection in the administration interface.
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 confidenceSQL injection vulnerability in the Kentico CMS administration interface affecting versions 10 before 10.0.50 and 11 before 11.0.3. The vulnerability allows authenticated administrators to inject malicious SQL queries through unsanitized input fields in the admin panel.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 Kentico CMS installationCheck for Kentico by looking for the /CMSPages/ or /CMSAdminControls/ paths in the web root, or search for 'Kentico' in site headers or footer branding.Affected if Kentico CMS is present in the environment
-
Determine installed Kentico versionLocate the version file or DLL. Typically found in the Bin folder as CMS.Base.dll version property, or in the ~/App_Data/CMS_Data/system.ini file, or check the CMS version in the admin dashboard under 'About' or 'Version info'.Affected if Version is >= 10.0.0 and < 10.0.50, OR >= 11.0.0 and < 11.0.3
-
Verify admin interface accessibilityCheck if the /cmsadmin/ or /admin/ path is routable from the network. Review IIS/web server configuration and firewall rules for external access to administrative URLs.Affected if The Kentico administration interface is accessible from untrusted networks or the internet
-
Confirm administrator authentication statusReview the Kentico user database table CMS_User or check the admin/user management panel for existing administrator accounts. Determine if any admin accounts are active or have elevated privileges.Affected if There is at least one active administrator account in the Kentico system
You are affected if Kentico CMS versions 10.0.0-10.0.49 or 11.0.0-11.0.2 are installed AND the admin interface is network-accessible AND an administrator account exists.
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 Kentico to version 10.0.50 or later, or version 11.0.3 or later. If immediate patching is not possible, restrict administrative access to trusted IP addresses and implement WAF rules for SQL injection detection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6843 — 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-6843 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