dbcve.org
XperienceApplication · Kentico

CVE-2019-25229

HIGH · 8.8 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 12.0.29 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An unrestricted file upload vulnerability in Kentico Xperience allows authenticated users with 'Read data' permissions to upload arbitrary file types via MVC form file uploader components. Attackers can manipulate file names and upload potentially malicious files to the system, enabling unauthorized file uploads.

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

Kentico Xperience CMS has an unrestricted file upload vulnerability in MVC form file uploader components. Authenticated users with only 'Read data' permissions can upload arbitrary file types by manipulating file names, allowing execution of malicious files on the server.

MitigationImplement strict allowlist-based file type validation on the server side for MVC form uploaders, reject files with dangerous extensions/content-types, and sanitize filenames. Additionally, store uploads outside webroot and use non-executable permissions.

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:<= 12.0.29

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Kentico Xperience installation and version
    Locate the Kentico Xperience installation and check the version number. This is typically visible in the CMS administration interface (Help > About) or in assembly metadata of the installed Kentico DLLs.
    Affected if The installed version is 12.0.29 or earlier.
  2. Verify MVC form file uploader is in use
    Determine whether the site uses MVC-based forms with file upload functionality. Check if any MVC-form based widgets or components that include the file uploader are deployed on the site.
    Affected if MVC form file upload components are present and active on the site.
  3. Check user permission configuration for file uploads
    Examine the permission model for the affected upload functionality. Determine whether users with only 'Read data' permissions are able to access or use the MVC form file upload feature.
    Affected if Users possessing only 'Read data' permissions can access or utilize the file upload functionality.
  4. Inspect file type validation configuration
    Review the server-side file type validation settings for MVC form uploaders. Look for allowlist-based validation configurations that restrict accepted file extensions and content types.
    Affected if No server-side allowlist validation is enforced, or validation can be bypassed by manipulating file names.

The environment is affected if it runs Kentico Xperience version 12.0.29 or earlier with MVC form file upload components enabled and users with limited 'Read data' permissions can access the upload functionality without proper allowlist validation.

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.29
Interim mitigation

Implement strict allowlist-based file type validation on the server side for MVC form uploaders, reject files with dangerous extensions/content-types, and sanitize filenames. Additionally, store uploads outside webroot and use non-executable permissions.

Recommended fix Moderate confidence

Kentico Xperience 12.0.174 or later (any version above 12.0.29)

  1. 1. Identify your current Kentico Xperience installation version by checking the Administration interface or the version.dll file in the installation directory
  2. 2. Backup your database and all application files before performing any upgrade
  3. 3. Download the latest Kentico Xperience version (12.0.174 or later) from the official Kentico download portal at www.kentico.com/download
  4. 4. Run the Kentico Xperience installer and follow the upgrade wizard, selecting your existing database when prompted
  5. 5. After upgrade completes, verify that the MVC form file uploader now properly validates file types and restricts uploads to allowed extensions only
  6. 6. Test the file upload functionality with various file types to confirm the restriction is working correctly
  7. 7. Review and apply any additional security settings recommended in the Kentico 12.0 release notes regarding file uploads
Caveat Minor: Custom MVC form adapters may require recompilation; verify custom file upload handlers are compatible with the new version

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

Fix this in Xperience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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