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 JPA Web API are typically accessible only to authenticated users. ### Patches The problem has been fixed in CUBA JPA Web API add-on 1.1.1. ### Workarounds A workaround for those who are unable to upgrade: [Disable Files Endpoint in CUBA Application](https://docs.jmix.io/jmix/files-vulnerabilities.html#disable-files-endpoint-in-cuba-application). ### References [Files Functionality Vulnerabilities :: Jmix Documentation](https://docs.jmix.io/jmix/files-vulnerabilities.html) Similar vulnerability in Jmix: [XSS in the /files Endpoint of the Generic REST API · Advisory · jmix-framework/jmix](https://github.com/jmix-framework/jmix/security/advisories/GHSA-x27v-f838-jh93)
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi | <1.1.1 | 1.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-32961 is considered a high-severity vulnerability due to the potential for remote code execution via malicious JavaScript.
To fix CVE-2025-32961, upgrade the affected version of the jpawebapi to version 1.1.1 or later.
CVE-2025-32961 can facilitate attacks that execute arbitrary JavaScript code in the user’s browser.
CVE-2025-32961 affects the jpawebapi version prior to 1.1.1.
You can determine vulnerability to CVE-2025-32961 by checking if your application is using jpawebapi versions below 1.1.1.