CVE-2025-32961

Workarounds

A workaround for those who are unable to upgrade: Disable Files Endpoint in CUBA Application.

References

Files Functionality Vulnerabilities :: Jmix Documentation

Similar vulnerability in Jmix: XSS in the /files Endpoint of the Generic REST API · Advisory · jmix-framework/jmix

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2025-32961 has a CVSS score of 6.4 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.1); upgrading removes the vulnerable code path.

Kodem intelligence

The problem has been fixed in CUBA JPA Web API add-on 1.1.1.

1. What is CVE-2025-32961? CVE-2025-32961 is a medium-severity cross-site scripting (XSS) vulnerability in com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi (maven), affecting versions < 1.1.1. It is fixed in 1.1.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-32961? CVE-2025-32961 has a CVSS score of 6.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi are affected by CVE-2025-32961? com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi (maven) versions < 1.1.1 is affected.
4. Is there a fix for CVE-2025-32961? Yes. CVE-2025-32961 is fixed in 1.1.1. Upgrade to this version or later.
5. Is CVE-2025-32961 exploitable, and should I be worried? Whether CVE-2025-32961 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32961 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32961? Upgrade com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi to 1.1.1 or later.