GHSA-hg25-w3vg-7279
MEDIUMXSS in the /download Endpoint of the JPA Web API
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
com.haulmont.addon.jpawebapi:jpawebapi-jpawebapiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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 JPA Web API are typically accessible only to authenticated users.
Patches
The problem has been fixed in CUBA JPA Web API add-on 1.1.1.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi | all versions | 1.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.haulmont.addon.jpawebapi:jpawebapi-jpawebapi to 1.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hg25-w3vg-7279 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hg25-w3vg-7279 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hg25-w3vg-7279. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hg25-w3vg-7279 in your dependencies?
O3 detects GHSA-hg25-w3vg-7279 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.