CVE-2024-58322
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 code into shipping options configuration. This could lead to potential theft of sensitive data by executing malicious scripts 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 confidenceA stored cross-site scripting vulnerability in Kentico Xperience allows attackers to inject malicious JavaScript into shipping options configuration fields. When other users view or interact with these shipping options in the admin panel or on the frontend, the injected script executes in their browsers, potentially stealing session cookies or other sensitive data.
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.
-
Identify installed Kentico Xperience versionAccess the admin panel System > Applications or check the version from the installation directory's assembly info. Alternatively, query the CMS_VersionInfo database table if direct database access is available.Affected if The installed version is 13.0.158 or lower.
-
Verify shipping options module is configuredNavigate to the shipping options configuration section in the Kentico admin panel (typically under E-commerce > Shipping > Shipping options). Confirm that shipping options exist in the system.Affected if Shipping options are configured and accessible in the admin panel.
-
Test shipping options fields for XSS vulnerabilityEdit an existing shipping option and attempt to inject HTML or script tags (e.g., <script>alert('XSS')</script> or <img src=x onerror=alert(1)>) into available text fields such as option name, description, or custom fields. Save the changes and view the shipping option.Affected if The injected HTML/script tags are rendered unescaped when the shipping option is displayed in the admin panel or on the frontend.
-
Inspect shipping options for existing malicious contentReview all shipping option records in the database table (typically CMS_ShippingOption or similar) or via the admin UI for any unexpected script tags, iframe elements, or event handlers (onclick, onerror, etc.) in text fields.Affected if Any shipping option records contain unsanitized HTML or JavaScript code that was not entered by an authorized administrator.
You are affected if your Kentico Xperience version is 13.0.158 or lower AND the shipping options feature is in use, particularly if configuration fields accept and render HTML markup without sanitization.
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.
From vendor dataImplement contextual output encoding for all shipping options configuration fields when rendered, and add server-side input validation to reject or sanitize HTML/script tags at the point of entry.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58322 — 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-58322 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