It technically possible for a user to upload a file to a conversation despite the file upload functionality being disabled.
The file upload functionality can be enabled or disabled for specific use cases through configuration. In case the functionality is disabled for at least one use case, the system nevertheless allows files to be uploaded through direct API requests. During the upload file, interception and allowed file type rules are still applied correctly.
If file sharing is generally enabled, this issue is not of concern.
References
Link | Resource |
---|---|
https://www.unblu.com/en/docs/latest/security-bulletins/#UBL-2025-002 | Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
23 Jun 2025, 19:22
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 4.3 |
CPE | cpe:2.3:a:unblu:spark:*:*:*:*:*:*:*:* | |
First Time |
Unblu spark
Unblu |
|
References | () https://www.unblu.com/en/docs/latest/security-bulletins/#UBL-2025-002 - Vendor Advisory |
24 Apr 2025, 15:15
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-284 |
23 Apr 2025, 14:08
Type | Values Removed | Values Added |
---|---|---|
Summary |
|
22 Apr 2025, 09:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-04-22 09:15
Updated : 2025-06-23 19:22
NVD link : CVE-2025-3518
Mitre link : CVE-2025-3518
CVE.ORG link : CVE-2025-3518
JSON object : View
Products Affected
unblu
- spark
CWE
CWE-284
Improper Access Control