dbcve.org
SitefinityApplication · Progress

CVE-2026-7195

HIGH · 8.1 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 14.4.8152 / 15.0.8234 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
CWE-20: Improper Input Validation in web services in Progress Sitefinity 14.1.x through 14.3.x, 14.4.x before 14.4.8152, 15.0.x before 15.0.8234, 15.1.x before 15.1.8335, 15.2.x before 15.2.8441, 15.3.x before 15.3.8531, and 15.4.x before 15.4.8630 allows a remote unauthenticated attacker to compromise the integrity and confidentiality of user accounts. Successful exploitation requires user interaction and a non-default site configuration.

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

Improper input validation (CWE-20) in Progress Sitefinity web services allows a remote unauthenticated attacker to compromise user account integrity and confidentiality. The vulnerability affects multiple version branches (14.1.x through 15.4.x) and requires both user interaction and a non-default site configuration for exploitation.

MitigationApply the vendor patches: upgrade to 14.4.8152, 15.0.8234, 15.1.8335, 15.2.8441, 15.3.8531, or 15.4.8630 and later. Review and harden non-default site configurations to reduce attack surface.

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:>= 14.1.7800, < 14.4.8152>= 15.0.8200, < 15.0.8234>= 15.1.8300, < 15.1.8335>= 15.2.8400, < 15.2.8441>= 15.3.8500, < 15.3.8531>= 15.4.8600, < 15.4.8630

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. Confirm Sitefinity CMS installation
    Locate the Sitefinity installation directory or check for Telerik.Sitefinity assemblies in the web application's bin folder. Look for Sitefinity-specific DLLs or configuration files such as SitefinityWebApp.dll or Telerik.Sitefinity.*.dll
    Affected if Sitefinity CMS is not present in the environment
  2. Identify installed Sitefinity version
    Check the assembly version of Telerik.Sitefinity.dll in the bin directory, or look in the web.config or administration dashboard for the Sitefinity version number
    Affected if The installed version falls within any of these ranges: 14.1.7800 to 14.4.8151, 15.0.8200 to 15.0.8233, 15.1.8300 to 15.1.8334, 15.2.8400 to 15.2.8440, 15.3.8500 to 15.3.8530, or 15.4.8600 to 15.4.8629
  3. Verify if web services are accessible
    Check the web.config for enabled web service endpoints under the system.web.extensions or system.serviceModel sections. Attempt to access common Sitefinity web service URLs such as /Sitefinity/Services/ or any custom .svc endpoints exposed by the application
    Affected if Web service endpoints are exposed and reachable without authentication
  4. Check for non-default site configuration
    Review Sitefinity configuration files (Sitefinity/Configuration/ folder) and the administration settings for any custom or non-standard configurations, particularly around authentication, authorization, or module settings that deviate from default installations
    Affected if A non-default site configuration is present in addition to the vulnerable version and exposed web services

A user is affected if Sitefinity CMS is installed with a version within the affected ranges AND web services are exposed AND a non-default site configuration exists, since the CVE requires both web service access and non-default settings for exploitation.

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.8152 / 15.0.8234 / 15.1.8335 or later
Fixed in 14.4.815215.0.823415.1.8335
Interim mitigation

Apply the vendor patches: upgrade to 14.4.8152, 15.0.8234, 15.1.8335, 15.2.8441, 15.3.8531, or 15.4.8630 and later. Review and harden non-default site configurations to reduce attack surface.

Recommended fix High confidence

Sitefinity 15.4.8630 or later (latest stable 15.x release)

  1. 1. Back up the Sitefinity database and all site files before proceeding with any upgrade.
  2. 2. Review the Sitefinity upgrade documentation for your current version at community.progress.com.
  3. 3. Download the latest Sitefinity release (15.4.8630 or higher) from the Progress Customer Portal.
  4. 4. Test the upgrade in a staging environment first to verify compatibility with custom modules and configurations.
  5. 5. Execute the upgrade following Progress's standard upgrade procedure for your deployment type.
  6. 6. After upgrade, verify that all web services are functioning correctly and test the fix by confirming the input validation is properly enforced.
  7. 7. Monitor for any errors in the Sitefinity error logs after deployment.
Caveat Major version upgrades in Sitefinity may require testing of custom modules, templates, and integrations; review breaking changes in the release notes before upgrading

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-2026-7195 — 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-2026-7195 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