| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Open-Xchange OX App Suite up to 7.6.3-rev77/8.35.111/8.38.82/8.39.79/8.40.57. This vulnerability affects unknown code. The manipulation results in ui layer. This vulnerability is reported as CVE-2025-30191. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Open-Xchange OX App Suite up to 7.6.3-rev77/8.35.111/8.38.82/8.39.79/8.40.57. Affected is an unknown code block. The manipulation with an unknown input leads to a ui layer vulnerability. CWE is classifying the issue as CWE-1021. The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusion about which interface the user is interacting with. This is going to have an impact on integrity. CVE summarizes:
Malicious content from E-Mail can be used to perform a redressing attack. Users can be tricked to perform unintended actions or provide sensitive information to a third party which would enable further threats. Attribute values containing HTML fragments are now denied by the sanitization procedure. No publicly available exploits are known
The advisory is available at documentation.open-xchange.com. This vulnerability is traded as CVE-2025-30191 since 03/18/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/31/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-37316). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 7.6.3-rev77
- 8.35.111
- 8.38.0
- 8.38.1
- 8.38.2
- 8.38.3
- 8.38.4
- 8.38.5
- 8.38.6
- 8.38.7
- 8.38.8
- 8.38.9
- 8.38.10
- 8.38.11
- 8.38.12
- 8.38.13
- 8.38.14
- 8.38.15
- 8.38.16
- 8.38.17
- 8.38.18
- 8.38.19
- 8.38.20
- 8.38.21
- 8.38.22
- 8.38.23
- 8.38.24
- 8.38.25
- 8.38.26
- 8.38.27
- 8.38.28
- 8.38.29
- 8.38.30
- 8.38.31
- 8.38.32
- 8.38.33
- 8.38.34
- 8.38.35
- 8.38.36
- 8.38.37
- 8.38.38
- 8.38.39
- 8.38.40
- 8.38.41
- 8.38.42
- 8.38.43
- 8.38.44
- 8.38.45
- 8.38.46
- 8.38.47
- 8.38.48
- 8.38.49
- 8.38.50
- 8.38.51
- 8.38.52
- 8.38.53
- 8.38.54
- 8.38.55
- 8.38.56
- 8.38.57
- 8.38.58
- 8.38.59
- 8.38.60
- 8.38.61
- 8.38.62
- 8.38.63
- 8.38.64
- 8.38.65
- 8.38.66
- 8.38.67
- 8.38.68
- 8.38.69
- 8.38.70
- 8.38.71
- 8.38.72
- 8.38.73
- 8.38.74
- 8.38.75
- 8.38.76
- 8.38.77
- 8.38.78
- 8.38.79
- 8.38.80
- 8.38.81
- 8.38.82
- 8.39.0
- 8.39.1
- 8.39.2
- 8.39.3
- 8.39.4
- 8.39.5
- 8.39.6
- 8.39.7
- 8.39.8
- 8.39.9
- 8.39.10
- 8.39.11
- 8.39.12
- 8.39.13
- 8.39.14
- 8.39.15
- 8.39.16
- 8.39.17
- 8.39.18
- 8.39.19
- 8.39.20
- 8.39.21
- 8.39.22
- 8.39.23
- 8.39.24
- 8.39.25
- 8.39.26
- 8.39.27
- 8.39.28
- 8.39.29
- 8.39.30
- 8.39.31
- 8.39.32
- 8.39.33
- 8.39.34
- 8.39.35
- 8.39.36
- 8.39.37
- 8.39.38
- 8.39.39
- 8.39.40
- 8.39.41
- 8.39.42
- 8.39.43
- 8.39.44
- 8.39.45
- 8.39.46
- 8.39.47
- 8.39.48
- 8.39.49
- 8.39.50
- 8.39.51
- 8.39.52
- 8.39.53
- 8.39.54
- 8.39.55
- 8.39.56
- 8.39.57
- 8.39.58
- 8.39.59
- 8.39.60
- 8.39.61
- 8.39.62
- 8.39.63
- 8.39.64
- 8.39.65
- 8.39.66
- 8.39.67
- 8.39.68
- 8.39.69
- 8.39.70
- 8.39.71
- 8.39.72
- 8.39.73
- 8.39.74
- 8.39.75
- 8.39.76
- 8.39.77
- 8.39.78
- 8.39.79
- 8.40.0
- 8.40.1
- 8.40.2
- 8.40.3
- 8.40.4
- 8.40.5
- 8.40.6
- 8.40.7
- 8.40.8
- 8.40.9
- 8.40.10
- 8.40.11
- 8.40.12
- 8.40.13
- 8.40.14
- 8.40.15
- 8.40.16
- 8.40.17
- 8.40.18
- 8.40.19
- 8.40.20
- 8.40.21
- 8.40.22
- 8.40.23
- 8.40.24
- 8.40.25
- 8.40.26
- 8.40.27
- 8.40.28
- 8.40.29
- 8.40.30
- 8.40.31
- 8.40.32
- 8.40.33
- 8.40.34
- 8.40.35
- 8.40.36
- 8.40.37
- 8.40.38
- 8.40.39
- 8.40.40
- 8.40.41
- 8.40.42
- 8.40.43
- 8.40.44
- 8.40.45
- 8.40.46
- 8.40.47
- 8.40.48
- 8.40.49
- 8.40.50
- 8.40.51
- 8.40.52
- 8.40.53
- 8.40.54
- 8.40.55
- 8.40.56
- 8.40.57
License
Website
- Vendor: https://www.open-xchange.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.4
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Ui layerCWE: CWE-1021
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/18/2025 CVE reserved10/31/2025 Advisory disclosed
10/31/2025 VulDB entry created
10/31/2025 VulDB entry last update
Sources
Vendor: open-xchange.comAdvisory: oxas-adv-2025-0002
Status: Confirmed
CVE: CVE-2025-30191 (🔒)
GCVE (CVE): GCVE-0-2025-30191
GCVE (VulDB): GCVE-100-330762
EUVD: 🔒
Entry
Created: 10/31/2025 10:55Updated: 10/31/2025 11:45
Changes: 10/31/2025 10:55 (62), 10/31/2025 11:45 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.