CVE-2025-32961
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2025-04-22

Last updated on: 2025-04-23

Assigner: GitHub, Inc.

Description
The Cuba JPA web API enables loading and saving any entities defined in the application data model by sending simple HTTP requests. Prior to version 1.1.1, 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 1.1.1. 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-06-16
AI Q&A
2025-04-23
EPSS Evaluated
2026-06-14
NVD
CVE-2025-32961
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 Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a low-severity cross-site scripting (XSS) issue in the Cuba JPA Web API’s /download endpoint. The problem occurs because the input parameter—which contains a file path and name—can be manipulated so that, if the file name ends with .html, the Content-Type header is set to 'text/html'. When a malicious file is already uploaded, this behavior can cause the browser to execute malicious JavaScript code. The issue affects versions earlier than 1.1.1, and it has been fixed in version 1.1.1. A temporary workaround is available by disabling the Files Endpoint in the CUBA Application. [4]

Impact Analysis

If exploited, this vulnerability could allow an attacker to execute malicious JavaScript code in your browser by tricking the system into serving a file with a misleading Content-Type header. This may lead to issues such as session hijacking or other unauthorized actions in the browser. However, the risk is somewhat reduced by the usual authentication requirements for accessing the application UI and API. [4]

Mitigation Strategies

Upgrade the JPA Web API to version 1.1.1 to patch the vulnerability. If upgrading immediately is not possible, apply the temporary workaround by disabling the Files Endpoint in the CUBA Application. [2, 4]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-32961. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart