dbcve.org
XperienceApplication · Kentico

CVE-2022-50685

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 13.0.56 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A stored cross-site scripting vulnerability in Kentico Xperience allows authenticated users to inject malicious scripts via XML file uploads as page attachments or metafiles. Attackers can upload malicious XML files that enable stored XSS, allowing malicious scripts to execute in users' browsers.

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 Xperience contains a stored cross-site scripting vulnerability where authenticated users can upload malicious XML files as page attachments or metafiles. The application fails to properly sanitize XML file content, allowing embedded malicious scripts to execute in users' browsers when the files are accessed or viewed.

MitigationImplement strict file type validation and content sanitization for file uploads, particularly rejecting or sanitizing XML files, and apply content security policy (CSP) headers to mitigate XSS execution.

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

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/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 checks

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

  1. Identify Kentico Xperience installation
    Check for Kentico Xperience by looking for its administrative interface paths (typically under /CMSModules or /CMSAdminControls) or check the application binaries for Kentico DLLs (e.g., CMS.Core.dll in the bin folder)
    Affected if The system is running Kentico Xperience CMS
  2. Determine installed version
    Check the version by viewing the assembly version of CMS.Core.dll in the bin directory, or access the version information through the Kentico administration interface (Help > About or Version information in the system menu)
    Affected if The installed version is 13.0.56 or lower
  3. Verify page attachment or metafile upload feature is enabled
    Check if the upload functionality exists by logging into the administration panel and navigating to Pages or Content, then attempting to access the Attachments or Metafiles section for any page or content item
    Affected if Users with authenticated access can upload files to pages or content items
  4. Confirm XML file uploads are permitted
    Review the allowed file extensions in the upload settings. Check the web.config or Kentico settings under Media & UI > File upload settings for the list of permitted file types
    Affected if XML file extension (.xml) is included in the allowed upload types

A user is affected if they are running Kentico Xperience version 13.0.56 or lower and have the file attachment/upload feature enabled with XML files permitted as an upload type.

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 13.0.56
Interim mitigation

Implement strict file type validation and content sanitization for file uploads, particularly rejecting or sanitizing XML files, and apply content security policy (CSP) headers to mitigate XSS execution.

Recommended fix Moderate confidence

Xperience 13.0.57 or later

  1. 1. Backup your current Xperience database and application files
  2. 2. Download Kentico Xperience version 13.0.57 or later from the official Kentico download portal
  3. 3. Review the hotfix release notes to confirm the XSS fix is included
  4. 4. Deploy the upgrade to a staging environment first
  5. 5. Test the XML file upload functionality to ensure the fix does not break legitimate uploads
  6. 6. Deploy the upgrade to production
Caveat Review release notes for any breaking changes between your current version and 13.0.57; test thoroughly in staging

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-2022-50685 — 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-2022-50685 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