Quick answers
- Is CVE-2026-7201 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7201 being exploited in the wild.
- How severe is CVE-2026-7201?
- High severity, with a CVSS score of 8.8, published 2 June 2026.
- Which products and versions are affected?
- Progress Sitefinity 15.2.x before 15.2.8441, 15.3.x before 15.3.8531, 15.4.x before 15.4.8630.
- Is there a fix for CVE-2026-7201?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7201 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-7201?
- Check whether you run Progress Sitefinity at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authorization bypass vulnerability (CWE-639) exists in Progress Sitefinity web services due to insufficient validation of user-controlled keys. A remote authenticated attacker can exploit this by providing specific identifiers to modify account properties belonging to other users. While the attack requires network access and low-privileged authentication, successful exploitation can lead to complete account compromise. The attacker must have prior knowledge of specific values (such as internal IDs) that are not generally exposed to low-privileged users. The issue is addressed in Sitefinity versions 15.2.8441, 15.3.8531, and 15.4.8630.
Affected products
- Progress Sitefinity 15.2.x before 15.2.8441, 15.3.x before 15.3.8531, 15.4.x before 15.4.8630
Timeline
- 2026-06-02: advisory: NVD and vendor advisory published