First published: Tue Apr 22 2025(Updated: )
### Impact 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. ### Patches The problem has been fixed in Jmix 1.6.2+ and 2.4.0+. ### Workarounds A workaround for those who are unable to upgrade: [Disable Files Endpoint in Jmix Application](https://docs.jmix.io/jmix/files-vulnerabilities.html#disable-files-endpoint-in-jmix-application).
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.jmix.rest:jmix-rest | >=2.0.0<2.4.0 | 2.4.0 |
maven/io.jmix.rest:jmix-rest | >=1.0.0<1.6.2 | 1.6.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-32951 is considered a high severity vulnerability due to the potential for executing malicious JavaScript code in the browser.
To fix CVE-2025-32951, upgrade to version 2.4.0 or later for the jmix-rest package.
CVE-2025-32951 affects jmix-rest versions from 1.0.0 to 1.6.2 and from 2.0.0 to 2.4.0.
CVE-2025-32951 allows for cross-site scripting (XSS) attacks through the manipulation of the Content-Type header.
CVE-2025-32951 is vulnerable to attacks via the input parameter consisting of file paths ending with .html.