dbcve.org
XperienceApplication · Kentico

CVE-2024-58318

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 13.0.162 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 attackers to inject malicious scripts via the rich text editor component for page and form builders. Attackers can exploit this vulnerability by entering malicious URIs, potentially 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 · high confidence

A stored cross-site scripting (XSS) vulnerability exists in Kentico Xperience's rich text editor component used for page and form builders. Attackers can inject malicious scripts through specially crafted URIs that get stored in the CMS. When users view content containing these malicious URIs, the embedded scripts execute in their browsers, potentially allowing session hijacking, credential theft, or unauthorized actions.

MitigationImplement strict input validation and output encoding for all URIs entered in the rich text editor, apply Content Security Policy (CSP) headers to mitigate XSS execution, and apply any vendor-supplied patches for Kentico Xperience.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed Kentico Xperience version
    Access the Kentico administration dashboard and navigate to the About section, or check the version.dll or assembly information in the deployment directory. Alternatively, query the CMS database version table if accessible.
    Affected if The installed version number is 13.0.162 or lower.
  2. Confirm the rich text editor component is in use
    Review the Kentico Xperience configuration for page types and form definitions. Check whether any page templates or form builder configurations include the Rich text editor (also called CKEditor in Kentico) input type.
    Affected if Rich text editor fields are defined in active page types or form builder forms within the CMS.
  3. Inspect rich text editor URI validation settings
    Access the Settings application in Kentico administration. Navigate to the Content -> Rich text editor settings section. Examine any configuration options related to URL protocols, link validation, or input filtering for the editor.
    Affected if URI validation is disabled, set to allow all protocols, or no strict filtering is configured for links inserted in the rich text editor.
  4. Review recent content entries in the CMS
    Use the Pages application to view recently created or modified page content. Check form builder submissions if available. Look for any entries containing unusual URI patterns, especially those with javascript: or data: prefixes, or URIs with encoded characters in link or anchor fields.
    Affected if Content exists in the CMS with suspicious URIs in rich text fields that may contain encoded XSS payloads.

You are affected if your Kentico Xperience installation is version 13.0.162 or lower and you have the rich text editor component enabled with active content that could contain malicious URIs.

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

Implement strict input validation and output encoding for all URIs entered in the rich text editor, apply Content Security Policy (CSP) headers to mitigate XSS execution, and apply any vendor-supplied patches for Kentico Xperience.

Recommended fix Moderate confidence

Kentico Xperience 13.0.163 or later (latest 13.0.x hotfix)

  1. 1. Navigate to the Kentico Xperience administration interface
  2. 2. Check the current version number in System > Application (or Help > About)
  3. 3. Obtain the latest Kentico Xperience 13.0.x hotfix from the Kentico Devnet portal or official download channels
  4. 4. Backup the Xperience database and website files before applying updates
  5. 5. Install the hotfix following Kentico's standard upgrade procedures
  6. 6. Verify the rich text editor now properly sanitizes malicious URIs
  7. 7. Test the patch by attempting to insert script-containing URIs in the rich text editor for page and form builders
Caveat Hotfixes are typically backward compatible; review release notes for any specific configuration changes

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

Fix this in Xperience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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