Skip to content

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

Moderate severity GitHub Reviewed Published Apr 22, 2025 in jmix-framework/jmix • Updated Apr 23, 2025

Package

maven io.jmix.rest:jmix-rest (Maven)

Affected versions

>= 1.0.0, < 1.6.2
>= 2.0.0, < 2.4.0

Patched versions

1.6.2
2.4.0

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 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.

References

@knstvk knstvk published to jmix-framework/jmix Apr 22, 2025
Published to the GitHub Advisory Database Apr 22, 2025
Reviewed Apr 22, 2025
Published by the National Vulnerability Database Apr 22, 2025
Last updated Apr 23, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

CVE ID

CVE-2025-32951

GHSA ID

GHSA-x27v-f838-jh93

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.