CVE-2019-25028 is a medium-severity (CVSS 6.1) CWE-80 vulnerability in com.vaadin:vaadin-bom. O3 Security confirms whether CVE-2019-25028 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Stored cross-site scripting in Grid component in Vaadin 7 and 8
Real-World Exposure
com.vaadin:vaadin-bom☕com.vaadin:vaadin-bom☕com.vaadin:vaadin-server☕com.vaadin:vaadin-serverReal-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
Missing variable sanitization in Grid component in com.vaadin:vaadin-server versions 7.4.0 through 7.7.19 (Vaadin 7.4.0 through 7.7.19), and 8.0.0 through 8.8.4 (Vaadin 8.0.0 through 8.8.4) allows attacker to inject malicious JavaScript via unspecified vector
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.vaadin:vaadin-bom | ≥ 7.4.0&&< 7.7.20 | 7.7.20 |
| ☕Maven | com.vaadin:vaadin-bom | ≥ 8.0.0&&< 8.8.5 | 8.8.5 |
| ☕Maven | com.vaadin:vaadin-server | ≥ 7.4.0&&< 7.7.20 | 7.7.20 |
| ☕Maven | com.vaadin:vaadin-server | ≥ 8.0.0&&< 8.8.5 | 8.8.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom. 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.vaadin:vaadin-bom to 7.7.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-25028 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 CVE-2019-25028 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 CVE-2019-25028. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2019-25028 in your dependencies?
O3 detects CVE-2019-25028 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.