CVE-2025-32960
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-04-22

Last updated on: 2025-04-23

Assigner: GitHub, Inc.

Description
The CUBA REST API add-on performs operations on data and entities. Prior to version 7.2.7, 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 version 7.2.7. A workaround is provided on the Jmix documentation website.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-04-22
Last Modified
2025-04-23
Generated
2026-04-26
AI Q&A
2025-04-23
EPSS Evaluated
2026-04-24
NVD
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-32960 is a cross-site scripting (XSS) vulnerability in the /files endpoint of the CUBA REST API add-on. The issue occurs when the input parameterβ€”composed of a file path and a file nameβ€”is manipulated so that if the file name ends with '.html', the service returns a Content-Type header of text/html. This behavior may allow malicious JavaScript code to be executed in the victim's browser if a malicious file has been uploaded beforehand. The problem is fixed in version 7.2.7 and, alternatively, the Files Endpoint can be disabled as a workaround. [4]


How can this vulnerability impact me?

If you interact with a system using the affected CUBA REST API add-on, an attacker might manipulate file names to trigger a cross-site scripting attack, potentially resulting in unauthorized execution of malicious JavaScript in your browser. However, the impact is mitigated by the fact that access to the API and the application's UI is generally restricted to authenticated users, which reduces the overall exposure. [4]


What immediate steps should I take to mitigate this vulnerability?

To mitigate the vulnerability, upgrade to version 7.2.7 of the CUBA REST API add-on where the issue is patched. If upgrading is not possible, apply the recommended workaround by disabling the Files Endpoint as described in the Jmix documentation. [1, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart