dbcve.org
SitefinityApplication · Progress

CVE-2019-7215

MEDIUM · 6.5 CVSS v3.0 Published 2019-06-06
Fix available
A fix is available. Upgrade to 7.0.5143 / 7.1.5243 or later.
See remediation →
74/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
Progress Sitefinity 10.1.6536 does not invalidate session cookies upon logouts. It instead tries to overwrite the cookie in the browser, but it remains valid on the server side. This means the cookie can be reused to maintain access to the account, even if the account credentials and permissions are changed.

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

Progress Sitefinity 10.1.6536 fails to invalidate session cookies server-side during logout. The application only attempts to overwrite the cookie in the browser, but the server-side session remains valid, allowing an attacker to reuse the old session cookie to maintain access even after credentials or permissions are changed.

MitigationUpgrade to a patched version of Sitefinity that properly invalidates session cookies server-side, or implement custom session invalidation logic that destroys the server-side session upon logout.

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:>= 7.0, < 7.0.5143>= 7.1, < 7.1.5243>= 7.2, < 7.2.5353>= 7.3, < 7.3.5693>= 8.0, < 8.0.5773>= 8.1, < 8.1.5863>= 8.2, < 8.2.5973>= 9.0, < 9.0.6063>= 9.1, < 9.1.6183>= 9.2, < 9.2.6274>= 10.0, < 10.0.6429>= 10.1, <= 10.1.6540

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
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Sitefinity version
    Locate the Sitefinity version by inspecting the assembly version in the bin folder (Telerik.Sitefinity.dll) or in the Sitefinity administrative interface under Administration > System > Version. Alternatively, check the web.config or AssemblyInfo.cs file.
    Affected if The installed version falls within any of the affected ranges: 7.0 to 7.0.5142, 7.1 to 7.1.5242, 7.2 to 7.2.5352, 7.3 to 7.3.5692, 8.0 to 8.0.5772, 8.1 to 8.1.5862, 8.2 to 8.2.5972, 9.0 to 9.0.6062, 9.1 to 9.1.6182, 9.2 to 9.2.6273, or 10.0 to 10.0.6428, or 10.1 to 10.1.6540.
  2. Confirm forms authentication is enabled
    Inspect the web.config file and look for the authentication element with mode set to 'Forms'. Also verify that a forms authentication cookie name is configured (typically 'SFAuthId' or similar).
    Affected if Forms authentication is enabled and the application relies on session cookies for authentication.
  3. Verify logout implementation
    Locate the logout code or page in the Sitefinity implementation. Examine whether the code calls Session.Abandon() or Session.Clear() in addition to FormsAuthentication.SignOut(). Also check if any custom session invalidation logic exists.
    Affected if The logout process only calls FormsAuthentication.SignOut() without explicitly invalidating the server-side session via Session.Abandon() or equivalent.
  4. Test session reuse after logout
    Log into the Sitefinity application, capture the session cookie value, perform logout, then replay the original cookie value in a new request to verify whether the session remains valid on the server side.
    Affected if The original session cookie remains valid and the server accepts it after logout, indicating server-side session was not invalidated.

You are affected if your Sitefinity version is within the affected ranges AND forms authentication is used AND the logout process does not explicitly invalidate server-side sessions.

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.

From vendor data
Upgrade available Upgrade to 7.0.5143 / 7.1.5243 / 7.2.5353 or later
Fixed in 7.0.51437.1.52437.2.5353
Interim mitigation

Upgrade to a patched version of Sitefinity that properly invalidates session cookies server-side, or implement custom session invalidation logic that destroys the server-side session upon logout.

Fix this in Sitefinity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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