CWE-20: Improper Input Validation in web services in Progress Sitefinity 14.1.x through…
CVE-2026-7195 is a high-severity improper input validation vulnerability in Sitefinity from Progress Software, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 14.4.0, 14.4.8152, 15.0.8234 as the first without the flaw, so updating Sitefinity to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Sitefinity to 14.4.0 or 14.4.8152 or 15.0.8234 or 15.1.8335, whichever matches your release line, or a later version.
- Read the advisory on community.progress.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Progress Software | Sitefinity | 14.1.0 up to, but not including, 14.4.0; 14.4.8100 up to, but not including, 14.4.8152; 15.0.8200 up to, but not including, 15.0.8234; 15.1.8300 up to, but not including, 15.1.8335; 15.2.8400 up to, but not including, 15.2.8441; 15.3.8500 up to, but not including, 15.3.8531; 15.4.8600 up to, but not including, 15.4.8630 | 14.4.0, 14.4.8152, 15.0.8234, 15.1.8335, 15.2.8441, 15.3.8531 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (progress.com) |
| CVSS 3.1 | 8.1 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Input Validation
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How developers prevent this class of flaw
- Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
- Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Sitefinity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 7.7 High severity
- 8.1 High severity
- 9.8 Critical severity
Recent Improper Input Validation vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 9.1 Critical severity
- 7.1 High severity
Spotted an error? Tell us.