CVE-2025-32961

Description

### 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)

How to fix CVE-2025-32961

To remediate CVE-2025-32961, upgrade the affected package to a fixed version below.

• —upgrade to 1.1.1 or later

Is CVE-2025-32961 being exploited?

Low — EPSS is 0.4%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 1.1.1

CVSS scores

References (7)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2025-32961
• PATCHgithub.com/cuba-platform/jpawebapi
• WEBdocs.jmix.io/jmix/files-vulnerabilities.html
• WEBdocs.jmix.io/jmix/files-vulnerabilities.html#disable-files-endpoint-in-cuba-application