dbcve.org
SitefinityApplication · Progress

CVE-2026-7198

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 15.4.8630 or later.
See remediation →
100/100
Remediation priority · Urgent
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
CWE-284: Improper Access Control in web services in Progress Sitefinity 15.4.8623 before 15.4.8630 allows a remote unauthenticated attacker to access content that should be restricted, resulting in full compromise of confidentiality, integrity, and availability of affected installations.

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 versions 15.4.8623 and earlier contain an improper access control vulnerability (CWE-284) in web services that allows remote unauthenticated attackers to bypass authorization checks and access restricted content. This enables full compromise of confidentiality, integrity, and availability as the attacker can read, modify, or delete sensitive data without any credentials.

MitigationUpgrade to Sitefinity version 15.4.8630 or later to apply the vendor patch. After upgrading, verify that access controls are properly enforced on all web services and review audit logs for any signs of exploitation.

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:>= 15.4.8623, < 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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
    Check the Sitefinity assembly version by inspecting the Telerik.Sitefinity.dll file in the /bin directory, or access the version endpoint at /Sitefinity/Version if available. You can also check the site footer or admin dashboard for version information.
    Affected if The installed version falls within the range 15.4.8623 through 15.4.8629 inclusive.
  2. Identify exposed web service endpoints
    Probe common Sitefinity web service paths such as /Sitefinity/Services/, /Api/, or custom .asmx endpoints. Use a browser or curl to send unauthenticated GET requests to these endpoints and observe if they return data or authentication errors.
    Affected if Web service endpoints are reachable from the network without providing credentials.
  3. Verify authentication enforcement on web services
    Attempt to access restricted web service resources or content that should require authentication. If content is returned without being prompted for login credentials, the authentication bypass is present.
    Affected if Unauthenticated requests successfully retrieve restricted content or data from web service endpoints.

If your Sitefinity version is between 15.4.8623 and 15.4.8629 and web service endpoints are accessible without authentication, your environment is affected by this CVE.

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 15.4.8630 or later
Fixed in 15.4.8630
Interim mitigation

Upgrade to Sitefinity version 15.4.8630 or later to apply the vendor patch. After upgrading, verify that access controls are properly enforced on all web services and review audit logs for any signs of exploitation.

Recommended fix High confidence

Sitefinity 15.4.8630 or later (latest 15.4.x release)

  1. 1. Back up the entire Sitefinity database and application files before proceeding with the upgrade.
  2. 2. Review the official Progress Sitefinity upgrade documentation at community.progress.com for your specific version path.
  3. 3. Ensure the production environment meets the system requirements for version 15.4.8630 or later.
  4. 4. Perform the upgrade by applying the Sitefinity 15.4.8630 (or latest 15.4.x) patch or upgrade package to your deployment.
  5. 5. After upgrade, verify that all Sitefinity services start correctly and the web application is accessible.
  6. 6. Test critical functionality including authentication, content access controls, and web services endpoints to confirm the vulnerability is remediated.
  7. 7. Monitor application logs for any errors or unusual access patterns following the upgrade.

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

Fix this in Sitefinity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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