CVE-2024-58317VulnerabilityPublished 18 Dec 2025

CVE-2024-58317: Kentico Xperience · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Affects Kentico XperienceSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Kentico Xperience	Affected =0	Fixed in–

AI-suggested

1. Review and update the web.config file in all Kentico Xperience deployments to ensure the 'requireSSL' attribute is correctly set to true for all cookies, particularly those related to administration and authentication. 2. Explicitly set the 'Secure' attribute on all session and authentication cookies to enforce transmission only over HTTPS. 3. Conduct a thorough audit of all web applications and services to verify that HTTPS is enforced site-wide, eliminating any possibility of HTTP fallback. 4. Implement HTTP Strict Transport Security (HSTS) headers to instruct browsers to only connect via HTTPS, reducing the risk of downgrade attacks. 5. Use web application firewalls (WAFs) to monitor and block suspicious traffic patterns that may indicate session hijacking attempts. 6. Regularly monitor logs for anomalous session activity, including unusual login times or IP addresses, to detect potential exploitation. 7. Educate development and operations teams on secure cookie handling best practices to prevent similar misconfigurations. 8. Stay updated with Kentico security advisories and apply patches or updates as they become available. 9. Consider implementing multi-factor authentication (MFA) on administrative accounts to add an additional layer of security beyond cookie-based sessions. 10. For legacy systems where immediate patching is not feasible, consider isolating administrative interfaces behind VPNs or IP whitelisting to limit exposure.

Description

CVE-2024-58317 is a medium severity vulnerability in Kentico Xperience affecting . NET Framework projects where administration cookies are set without the 'Secure' attribute. This misconfiguration allows cookies to be transmitted over non-HTTPS connections, potentially exposing session cookies to interception and session hijacking. The vulnerability arises from incorrect handling of the 'requireSSL' attribute in web.config, bypassing SSL enforcement for sensitive cookies. Exploitation requires no authentication or user interaction and can be performed remotely. Although no known exploits are currently reported in the wild, the risk to session confidentiality and authentication integrity is significant. European organizations using Kentico Xperience for content management or web administration should prioritize patching or configuration review. Countries with high adoption of . NET and Kentico platforms, and critical infrastructure relying on these systems, are at greater risk.

Impact

For European organizations, the vulnerability poses a risk of session hijacking attacks targeting administrative interfaces of Kentico Xperience deployments. Successful exploitation could allow attackers to gain unauthorized administrative access, leading to data breaches, content manipulation, or disruption of web services. This is particularly critical for organizations managing sensitive or regulated data, such as financial institutions, healthcare providers, and government agencies. The exposure of session cookies over non-HTTPS channels undermines confidentiality and integrity of authentication sessions. Given the widespread use of .NET technologies and Kentico in Europe, especially in sectors relying on web content management, the vulnerability could affect a broad range of organizations. The risk is heightened in environments where HTTPS enforcement is inconsistent or where legacy configurations persist. Additionally, attackers could leverage this vulnerability as a foothold for further lateral movement or privilege escalation within compromised networks. The absence of known exploits currently reduces immediate risk but does not eliminate the potential for future attacks. Therefore, European organizations must assess their exposure and implement mitigations promptly to protect critical web administration interfaces.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Dec 2025, 21:14 UTC

Technical details

References

Community reviews

Related threats