dbcve.org
XperienceApplication · Kentico

CVE-2024-58317

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to after 13.0.164 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
A cookie security configuration vulnerability in Kentico Xperience allows attackers to bypass SSL requirements when setting administration cookies via web.config. The vulnerability affects .NET Framework projects by incorrectly handling the 'requireSSL' attribute, potentially compromising session security and authentication state.

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 confidence

Kentico Xperience for .NET Framework contains a cookie security misconfiguration where the requireSSL attribute in web.config is incorrectly handled for administration cookies. This allows cookies to be set without the secure flag, potentially allowing session theft or authentication bypass via interception of unencrypted cookie transmission.

MitigationReview and correctly configure the requireSSL attribute for all cookies in web.config, ensuring administration cookies are set with requireSSL='true' to enforce Secure flag and HTTPS-only transmission.

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

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. Check installed Kentico Xperience version
    Locate the Kentico Xperience version by checking the assembly version of CMS.dll in the bin folder, or log into the administration interface and navigate to the 'About' or 'Help' section where version information is displayed
    Affected if Version is 13.0.164 or lower
  2. Locate the web.config file
    Find the web.config file in the root directory of the Kentico Xperience application (typically in the CMS folder or site root)
    Affected if web.config exists and is readable
  3. Inspect requireSSL attribute configuration
    Open web.config and search for 'requireSSL' within the <system.web> and <httpModules> or <system.webServer> sections, particularly looking for cookie settings under FormsAuthentication or Session configurations
    Affected if requireSSL is set to 'false' or is missing for authentication/session cookies, or administration cookie configurations omit the secure flag
  4. Verify cookie configuration for admin area
    Search web.config for sections related to admin authentication cookies - look for FormsAuthentication element, cookie settings, and any 'CookieDomain' or 'CookiePath' configurations
    Affected if Administration cookies do not have requireSSL='true' explicitly set, or configuration allows non-HTTPS cookie transmission for admin areas
  5. Test live cookie attributes (optional)
    If the application is accessible, use browser developer tools (F12) to inspect cookies set during admin login - check the 'Secure' flag on cookies with names like '.ASPXAUTH', 'CMSPreferredCulture', or other session-related cookies
    Affected if Admin cookies are set without the Secure flag when accessing the admin interface over HTTPS

If Kentico Xperience version is 13.0.164 or lower AND web.config lacks requireSSL='true' for administration cookies, the environment is affected by this vulnerability.

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

Review and correctly configure the requireSSL attribute for all cookies in web.config, ensuring administration cookies are set with requireSSL='true' to enforce Secure flag and HTTPS-only transmission.

Recommended fix Moderate confidence

Xperience 13.0.165 or later (latest 13.0.x hotfix)

  1. Obtain the latest Kentico Xperience 13.0.x hotfix from the Kentico DevNet portal (devnet.kentico.com) or official Kentico distribution channels
  2. Backup your current project files and database before applying any updates
  3. Apply the hotfix to your Xperience installation, ensuring all assemblies and configuration files are updated
  4. Verify the web.config settings for cookie security: ensure forms authentication and session state cookies have requireSSL="true" set appropriately
  5. Test the application thoroughly in a staging environment, specifically verifying that administration cookies are only sent over HTTPS
  6. Deploy the fixed version to production
Caveat Review release notes for any breaking changes between your current version and the target hotfix; test thoroughly before production deployment

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

Fix this in Xperience Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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