CVE-2024-58323
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 · uneditedA stored cross-site scripting vulnerability in Kentico Xperience allows attackers to inject malicious scripts via the Checkbox form component. This allows malicious scripts to execute in users' browsers by exploiting HTML support in the form builder.
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 confidenceA stored cross-site scripting vulnerability exists in Kentico Xperience's Checkbox form component. Attackers can inject malicious scripts through the form builder's HTML support, which persists and executes in users' browsers when they view or interact with the compromised form.
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<= 13.0.158CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Kentico Xperience versionLocate the Kentico Xperience version in the administration interface (typically under Help > About) or check the version in the CMS DLL file properties or release notesAffected if Version number is 13.0.158 or lower
-
Identify forms using Checkbox componentsReview all forms in the form builder to identify any that include the Checkbox form componentAffected if Forms exist that contain Checkbox components and those forms accept user input
-
Inspect form builder HTML input settingsExamine the Checkbox component configuration in the form builder for any HTML or rich text input support settings that allow raw HTMLAffected if HTML input or rich text editing is enabled on Checkbox form fields
-
Review stored form configurations for suspicious contentExamine the database tables storing form definitions (specifically Checkbox field configurations) for any stored script tags, JavaScript event handlers, or suspicious HTML markupAffected if Any Checkbox form field configuration contains script tags, javascript: handlers, or other XSS vectors in stored values
-
Audit form submission data for injected scriptsReview form submission data stored in the database for any entries containing script tags or HTML that could indicate prior exploitationAffected if Form submissions contain unsanitized script tags or HTML with event handlers
You are affected if running Kentico Xperience version 13.0.158 or lower and have forms using the Checkbox component with HTML input support enabled or configured.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper input validation and output encoding for the Checkbox form component. Restrict or sanitize HTML input in the form builder to prevent script injection while preserving legitimate functionality.
Kentico Xperience version > 13.0.158 (contact Kentico support for specific hotfix)
- Upgrade Kentico Xperience to a version newer than 13.0.158 that includes the security fix for the Checkbox form component XSS vulnerability
- Contact Kentico support or consult the official release notes at devnet.kentico.com to confirm the specific hotfix version containing the remediation
- After upgrading, verify that the Checkbox form component properly sanitizes HTML input to prevent XSS attacks
- Test the form builder functionality to ensure the fix does not break legitimate HTML rendering capabilities in forms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-58323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-58323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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