dbcve.org
SitefinityApplication · Progress

CVE-2024-11627

HIGH · 8.1 CVSS v3.1 Published 2025-01-07
Fix available
A fix is available. Upgrade to 14.4.8143 / 15.0.8230 or later.
See remediation →
88/100
Remediation priority · High
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
: Insufficient Session Expiration vulnerability in Progress Sitefinity allows : Session Fixation.This issue affects Sitefinity: from 4.0 through 14.4.8142, from 15.0.8200 through 15.0.8229, from 15.1.8300 through 15.1.8327, from 15.2.8400 through 15.2.8421.

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

Session fixation vulnerability in Progress Sitefinity where the application fails to properly invalidate or regenerate session IDs during user authentication, allowing an attacker to set or fix a session ID before a user logs in and subsequently hijack the authenticated session.

MitigationUpdate Sitefinity to a version beyond the affected ranges (14.4.8142, 15.0.8229, 15.1.8327, or 15.2.8421) or apply the vendor's security patch to ensure session IDs are regenerated upon authentication.

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
SitefinityApplication
Affected:>= 4.0, < 14.4.8143>= 15.0.8200, < 15.0.8230>= 15.1.8300, < 15.1.8328>= 15.2.8400, < 15.2.8422

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Determine installed Sitefinity version
    Log into the Sitefinity admin dashboard and navigate to Administration > Settings > About, or check the Sitefinity assembly version in the bin folder (Telerik.Sitefinity.dll). Compare the version number against the affected ranges: 4.0 to 14.4.8142, 15.0.8200 to 15.0.8229, 15.1.8300 to 15.1.8327, or 15.2.8400 to 15.2.8421.
    Affected if The installed version falls within any of the listed ranges.
  2. Locate the web.config file
    Find the web.config file in the root of the Sitefinity application directory. This file controls session and authentication settings.
    Affected if The web.config file is missing or not accessible for review.
  3. Check Forms Authentication configuration
    In the web.config file, locate the <forms> element under <authentication mode="Forms">. Verify if the slidingExpiration attribute is set to "true" and observe the timeout value.
    Affected if Forms Authentication is enabled with slidingExpiration="true" and the session fixation vulnerability exists in the affected version.
  4. Verify session state configuration
    In web.config, locate the <sessionState> element under <system.web>. Check if sessionState is enabled (mode="InProc", "SQLServer", or "StateServer").
    Affected if Session state is enabled and the application runs an affected version.
  5. Check for session regeneration on login
    Inspect custom authentication code or Sitefinity login workflow to determine if SessionID is regenerated after successful authentication. This typically involves checking if System.Web.SessionState.HttpSessionIDManager is used to call InitializeRequest and that a new session cookie is issued post-login.
    Affected if The authentication workflow does not regenerate session IDs after login, leaving sessions vulnerable to fixation.

The environment is affected if Sitefinity is installed at a version within the affected ranges (4.0-14.4.8142, 15.0.8200-15.0.8229, 15.1.8300-15.1.8327, or 15.2.8400-15.2.8421) and session IDs are not regenerated upon user authentication.

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 14.4.8143 / 15.0.8230 / 15.1.8328 or later
Fixed in 14.4.814315.0.823015.1.8328
Interim mitigation

Update Sitefinity to a version beyond the affected ranges (14.4.8142, 15.0.8229, 15.1.8327, or 15.2.8421) or apply the vendor's security patch to ensure session IDs are regenerated upon authentication.

Recommended fix High confidence

14.4.8143 (or latest 14.4.x); 15.0.8230 (or latest 15.0.x); 15.1.8328 (or latest 15.1.x); 15.2.8422 (or latest 15.2.x)

  1. Back up the current Sitefinity database and all custom code/configurations before upgrading.
  2. Review the Progress Sitefinity upgrade documentation for your current version to ensure compatibility.
  3. Test the upgrade in a non-production environment first to identify any potential issues.
  4. Upgrade Sitefinity to version 14.4.8143 or higher (for versions 4.0-14.4.x).
  5. If running version 15.0.x, upgrade to version 15.0.8230 or higher.
  6. If running version 15.1.x, upgrade to version 15.1.8328 or higher.
  7. If running version 15.2.x, upgrade to version 15.2.8422 or higher.
  8. Verify the upgrade was successful and test application functionality.
Caveat Review upgrade notes for your specific version branch as custom modules or configurations may require updates; major version jumps may have breaking changes

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

Fix this in Sitefinity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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