dbcve.org
XperienceApplication · Kentico

CVE-2022-50686

HIGH · 7.5 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 12.0 or later.
See remediation →
84/100
Remediation priority · High
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
An information disclosure vulnerability in Kentico Xperience allows attackers to view sensitive stack trace details via Portal Engine form control error messages. Detailed error messages can expose internal system information and potentially reveal implementation details to unauthorized users.

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 Portal Engine form control error messages expose detailed stack trace information to unauthorized users, allowing attackers to gather sensitive internal system details, file paths, and implementation specifics that could facilitate further attacks.

MitigationConfigure custom error pages or disable detailed exception output in production environments to prevent stack trace disclosure; ensure only generic user-friendly messages are displayed while detailed logs remain accessible only to administrators.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Check installed Kentico Xperience version
    Locate the version file or assembly information for your Kentico Xperience installation. Common locations include the CMSApp_Global.asax file, bin folder DLL properties, or the version.xml file in the installation directory.
    Affected if The installed version is 12.0 or lower
  2. Verify Portal Engine is in use
    Check your application configuration files (typically web.config) for the presence of Portal Engine-related settings or examine the URL patterns and page templates in the CMS administration interface to confirm Portal Engine is being used.
    Affected if Portal Engine is enabled and handles form controls in your environment
  3. Inspect custom error page configuration
    Examine the web.config file's system.web/customErrors section and look for the mode attribute setting. Also check the CMSweb.config for any Kentico-specific error handling settings.
    Affected if Custom errors are set to Off or RemoteOnly, or detailed exceptions are explicitly enabled
  4. Test error message output from public-facing forms
    Submit invalid or unexpected input to Portal Engine form controls on a non-authenticated page. Observe whether the returned error pages or messages contain stack traces, file paths, or internal implementation details.
    Affected if Error responses display detailed stack traces or internal system information to unauthorized users

You are affected if your Kentico Xperience version is 12.0 or lower, Portal Engine is active, and error responses expose stack trace or internal system details 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 custom error pages or disable detailed exception output in production environments to prevent stack trace disclosure; ensure only generic user-friendly messages are displayed while detailed logs remain accessible only to administrators.

Recommended fix Moderate confidence

Kentico Xperience 12.0 (or latest stable release) - contact Kentico support for exact patched version

  1. 1. Obtain the latest Kentico Xperience release from the official Kentico download portal or management system
  2. 2. Review the Kentico upgrade documentation for version 12.0 to the latest available version
  3. 3. Perform a full backup of the existing Xperience database and application files
  4. 4. Execute the upgrade following the documented upgrade procedure
  5. 5. Verify that detailed error messages and stack traces are no longer exposed in Portal Engine form controls
  6. 6. Test Portal Engine form functionality to ensure normal operation after upgrade
Caveat Review upgrade notes for potential breaking changes between versions; custom form controls may require testing

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

Fix this in Xperience Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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