CVE-2026-7201
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 · uneditedCWE-639: Authorization Bypass Through User-Controlled Key in web services in Progress Sitefinity 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 authenticated attacker to modify account properties of other users, potentially leading to account compromise. Successful exploitation requires knowledge of values that are not generally exposed to low-privileged users.
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 confidenceThis is an authorization bypass vulnerability (CWE-639) in Progress Sitefinity CMS where an authenticated attacker can manipulate user-controlled keys to modify account properties of other users, potentially leading to account takeover. The attacker needs knowledge of certain values not exposed to low-privileged users.
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>= 15.2.8400, < 15.2.8441>= 15.3.8500, < 15.3.8531>= 15.4.8600, < 15.4.8630CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Sitefinity CMS installed versionLocate the Sitefinity assembly file (typically Telerik.Sitefinity.dll) in the bin directory and read its version property, or check the version in the Sitefinity administration dashboard under Administration > System > AboutAffected if The installed version falls within any of these ranges: 15.2.8400 to 15.2.8440 (exclusive of patched versions), 15.3.8500 to 15.3.8530 (exclusive of patched versions), or 15.4.8600 to 15.4.8629 (exclusive of patched versions)
-
Confirm user management module is activeVerify that the Users module or Membership functionality is enabled in Sitefinity by checking the site configuration or attempting to access the Users section in the administration interfaceAffected if User management features are enabled and the CMS version is within the affected ranges listed above
You are affected if your Sitefinity CMS version is 15.2.8400-15.2.8440, 15.3.8500-15.3.8530, or 15.4.8600-15.4.8629 and the Users module is active.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.2.844115.3.853115.4.8630
Apply the vendor patches by upgrading to Sitefinity 15.2.8441, 15.3.8531, or 15.4.8630 and later versions. Restrict access to sensitive user identifiers in the meantime.
Sitefinity 15.2.8441, 15.3.8531, or 15.4.8630 (recommended: latest 15.4.x stable release)
- 1. Identify your current Sitefinity version from the administration dashboard or project configuration.
- 2. Determine which version branch you are on (15.2.x, 15.3.x, or 15.4.x).
- 3. Download the appropriate fixed version from the Progress Sitefinity customer portal or official distribution channels.
- 4. Back up your current Sitefinity application, database, and configuration files.
- 5. Deploy the fixed version (15.2.8441, 15.3.8531, or 15.4.8630) following standard Sitefinity upgrade procedures.
- 6. Verify the web services endpoint access controls are functioning correctly after upgrade.
- 7. Test that users can only modify their own account properties and not those of other users.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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