dbcve.org
XperienceApplication · Kentico

CVE-2019-12102

CRITICAL · 9.1 CVSS v3.0 Published 2019-05-22
Fix available
A fix is available. Upgrade to after 12.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Kentico 11 through 12 lets attackers upload and explore files without authentication via the cmsmodules/medialibrary/formcontrols/liveselectors/insertimageormedia/tabs_media.aspx URI. NOTE: The vendor disputes the report because the researcher did not configure the media library permissions correctly. The vendor states that by default all users can read/modify/upload files, and it’s up to the administrator to decide who should have access to the media library and set the permissions accordingly. See the vendor documentation in the references for more information

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 confidence

Kentico 11 through 12 contains an unauthenticated file upload and exploration vulnerability in the media library functionality accessible via cmsmodules/medialibrary/formcontrols/liveselectors/insertimageormedia/tabs_media.aspx, allowing remote attackers to upload and browse files without authentication.

MitigationConfigure media library permissions to restrict write access to authorized users only per Kentico documentation; consider applying any vendor patches and implementing additional access controls.

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
XperienceApplication
Affected:>= 11.0.0, <= 12.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Kentico version
    Locate the Kentico installation directory and check the version.dll or CMSDLLVer.txt file, or query the CMS_SystemVersion database table. Compare against affected range 11.0.0 to 12.0.
    Affected if Installed version is >= 11.0.0 and <= 12.0
  2. Verify media library module is installed
    Check for the presence of the Medialibrary module in Kentico administration under Modules, or verify the cmsmodules/medialibrary directory exists in the web root.
    Affected if Media library module is present and enabled
  3. Confirm vulnerable endpoint exists
    Check if the file cmsmodules/medialibrary/formcontrols/liveselectors/insertimageormedia/tabs_media.aspx exists in the web application directory.
    Affected if The tabs_media.aspx file exists in the expected path
  4. Test unauthenticated access to media library
    Attempt to access the media library selector endpoint without authentication using a browser or HTTP request tool: /cmsmodules/medialibrary/formcontrols/liveselectors/insertimageormedia/tabs_media.aspx
    Affected if The page loads or responds without requiring login credentials
  5. Check media library permissions configuration
    In Kentico administration, navigate to Media Library > Permissions and verify whether anonymous or unauthenticated users have write/create permissions.
    Affected if Anonymous or unauthenticated users have write access to any media library

Environment is affected if running Kentico 11.0.0 through 12.0 with the media library module enabled and the vulnerable tabs_media.aspx endpoint accessible to unauthenticated users.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.0
Interim mitigation

Configure media library permissions to restrict write access to authorized users only per Kentico documentation; consider applying any vendor patches and implementing additional access controls.

Recommended fix Moderate confidence
  1. Review media library permissions in Kentico Administration interface under the Media library module
  2. Configure appropriate role-based permissions for the Media Library to restrict unauthorized access
  3. Ensure that only authenticated users with proper roles have upload, modify, and delete permissions
  4. If the media library functionality is not needed, consider disabling or restricting access to the /cmsmodules/medialibrary/ path
  5. Implement proper authentication requirements for the media library endpoints via web.config or IIS configuration if the built-in permissions are insufficient
  6. Audit existing user roles and permissions to ensure no overly permissive default assignments exist

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xperience Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-12102 — 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-2019-12102 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