# CVE-2025-32951: io.jmix.rest:jmix-rest allows XSS in the /files Endpoint of the Generic REST API

> Attackers can execute malicious JavaScript in browsers via the /files endpoint if a malicious file is uploaded, affecting Jmix REST API users.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-x27v-f838-jh93

## What is CVE-2025-32951?

CVE-2025-32951 is a medium-severity cross-site scripting vulnerability in jmix-framework jmix, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jmix is a set of libraries and tools to speed up Spring Boot data-centric application development. In versions 1.0.0 to 1.6.1 and 2.0.0 to 2.3.4, 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. This issue has been patched in versions 1.6.2 and 2.4.0. A workaround is provided on the Jmix documentation website.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-32951?

4 open source packages ship an affected version, including io.jmix.rest:jmix-rest. It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jmix.rest:jmix-rest` | Maven | From 1.0.0 | 1.6.2 |
| `io.jmix.rest:jmix-rest` | Maven | From 1.0.0 | 1.6.2 |
| `io.jmix.rest:jmix-rest` | Maven | From 2.0.0 | 2.4.0 |
| `io.jmix.rest:jmix-rest` | Maven | From 2.0.0 | 2.4.0 |

Products: Haulmont Cuba Platform, Haulmont Cuba Rest Api, Haulmont Jmix Framework, Haulmont Jpa Web Api.

## How do I fix CVE-2025-32951?

Upgrade io.jmix.rest:jmix-rest to a fixed version for your release line: 1.6.2 or 2.4.0.

## Is CVE-2025-32951 being exploited?

There is no known exploitation of CVE-2025-32951 in the wild and no public exploit code.

## Other vulnerabilities in jmix-framework jmix

- [CVE-2025-32952](https://insights.sbomify.com/CVE-2025-32952/): io.jmix.localfs:jmix-localfs affected by DoS in the Local File Storage (medium 6.5)
- [CVE-2018-20663](https://insights.sbomify.com/CVE-2018-20663/): The Reporting Addon for CUBA Platform has Persistent XSS (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32951 and fix it if it is affected.

What it is: CVE-2025-32951 is a medium-severity cross-site scripting vulnerability in jmix-framework jmix, published on 22 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32951 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jmix.rest:jmix-rest (Maven): affected from 1.0.0; fixed in 1.6.2
- io.jmix.rest:jmix-rest (Maven): affected from 1.0.0; fixed in 1.6.2
- io.jmix.rest:jmix-rest (Maven): affected from 2.0.0; fixed in 2.4.0
- io.jmix.rest:jmix-rest (Maven): affected from 2.0.0; fixed in 2.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32951/ (Markdown: https://insights.sbomify.com/CVE-2025-32951/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32951
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32951
- OSV: https://osv.dev/vulnerability/CVE-2025-32951

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32951/
Summaries are generated and may contain mistakes; the official description above is the record.