CVE-2025-3519: Replace uploaded files knowing the file upload ID
An authorization bypass in Unblu Spark allows a participant of a conversation to replace an existing, uploaded file.
Every uploaded file in Unblu gets assigned with a randomly generated Universally Unique ID (UUID). In case a participant of this or another conversation gets access to such a file ID, it can be used to replace the file without changing the file name and details or the name of the user who uploaded the file. During the upload, file interception and allowed file type rules are still applied correctly.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-3519?
CVE-2025-3519 is classified as a high severity vulnerability due to the potential for unauthorized file replacement.
How do I fix CVE-2025-3519?
To fix CVE-2025-3519, users should update to the latest version of Unblu Spark that contains the necessary security patches.
What kind of attack does CVE-2025-3519 facilitate?
CVE-2025-3519 facilitates an authorization bypass attack allowing unauthorized users to replace existing uploaded files.
Who is affected by CVE-2025-3519?
Users of Unblu Spark are affected by CVE-2025-3519, particularly those participating in conversations where file uploads occur.
Is CVE-2025-3519 exploitable remotely?
Yes, CVE-2025-3519 is exploitable remotely by any participant in a conversation using Unblu Spark.