The input parameter, which consists of a file path and name, can be manipulated to return the Content-Type header with text/html if the name part ends with .html. This could allow malicious JavaScript code to be executed in the browser. For a successful attack, a malicious file needs to be uploaded beforehand.
The severity of the vulnerability is mitigated by the fact that the application UI and the generic REST API are typically accessible only to authenticated users. Additionally, the /files endpoint in Jmix requires specific permissions and is disabled by default.
The problem has been fixed in Jmix 1.6.2+ and 2.4.0+.
A workaround for those who are unable to upgrade: Disable Files Endpoint in Jmix Application.
{ "github_reviewed_at": "2025-04-22T16:55:13Z", "severity": "MODERATE", "nvd_published_at": "2025-04-22T18:15:59Z", "github_reviewed": true, "cwe_ids": [ "CWE-79" ] }