CVE-2019-25075 — gravitee-api-management
MEDIUMCVE-2019-25075 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in io.gravitee.apim:gravitee-api-management. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for io.gravitee.apim:gravitee-api-management — see the affected versions and patch details below.
Path Traversal in Gravitee API Management
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.gravitee.apim:gravitee-api-managementReal-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
HTML injection combined with path traversal in the Email service in Gravitee API Management before 1.25.3 allows anonymous users to read arbitrary files via a /management/users/register request.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.gravitee.apim:gravitee-api-management | all versions | 1.25.3io.gravitee.apim:gravitee-api-management:1.25.3 |
Affected Products
api managementgraviteeResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.gravitee.apim:gravitee-api-management, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.gravitee.apim:gravitee-api-management to 1.25.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-25075 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2019-25075 in your dependencies?
Find it across Maven, including transitive dependencies.