dbcve.org
XperienceApplication · Kentico

CVE-2019-25228

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 12.0.47 or later.
See remediation →
62/100
Remediation priority · Elevated
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 leak virtual context URLs via the HTTP Referer header when users interact with third-party domains. Sensitive virtual context information can be exposed to external domains through page builder interactions and link/image loading.

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 fails to properly restrict virtual context URLs from being transmitted in the HTTP Referer header when users interact with third-party domains through page builder components. This allows sensitive internal path information to leak to external websites when users click links or load images within the page builder interface.

MitigationImplement strict Referrer-Policy headers (e.g., 'same-origin' or 'strict-origin-when-cross-origin') and review page builder component configuration to prevent virtual context URLs from being exposed in outbound requests to third-party domains.

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.47

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Kentico Xperience version
    Check the CMS folder for a version file or assembly information, typically found in bin/CMS.dll version property or in the administration interface under 'About' section
    Affected if Version is 12.0.47 or lower (12.0.x <= 12.0.47)
  2. Confirm page builder is in use
    Check for presence of page builder-related assemblies (CMS.PageEngine.*) in the bin folder or review the application for custom page builder components in the ~/CMSModules/PageBuilder directory
    Affected if Page builder components and associated modules are installed and active in the application
  3. Inspect HTTP response headers for Referrer-Policy
    Use browser developer tools, curl -I, or a header scanning tool to examine HTTP responses from the Kentico site; look for the Referrer-Policy header
    Affected if Referrer-Policy header is missing, set to unsafe-url, or not configured to restrict cross-origin referrer leakage
  4. Verify virtual context URL leakage in referer
    Use browser network monitoring (F12 > Network tab) while interacting with page builder components that reference third-party domains; examine the Referer header sent in outbound requests
    Affected if The Referer header contains internal virtual context paths (such as /Kentico.VirtualContext/ or similar internal URLs) when requests go to third-party domains

You are affected if running Kentico Xperience 12.0.47 or lower, the page builder is active, and the Referer header exposes internal virtual context URLs to third-party domains.

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

Implement strict Referrer-Policy headers (e.g., 'same-origin' or 'strict-origin-when-cross-origin') and review page builder component configuration to prevent virtual context URLs from being exposed in outbound requests to third-party domains.

Recommended fix Moderate confidence

Kentico Xperience 12.0.x latest stable release (version > 12.0.47) or migrate to latest 13.x branch

  1. 1. Identify all Kentico Xperience installations in your environment running version 12.0.47 or earlier
  2. 2. Review Kentico's official security advisory for CVE-2019-25228 to obtain the specific hotfix or patch file
  3. 3. Download the appropriate hotfix package from devnet.kentico.com or the Kentico download section
  4. 4. Back up your database and application files before applying any updates
  5. 5. Apply the hotfix following Kentico's standard hotfix installation procedure
  6. 6. Verify the fix by testing page builder interactions and checking that virtual context URLs are not leaked via the HTTP Referer header
  7. 7. Confirm the updated version after installation
Caveat Review Kentico release notes for any breaking changes between 12.0.47 and the target version; some configuration adjustments may be needed

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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