How severe is CVE-2019-25028?

CVE-2019-25028 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-25028?

CVE-2019-25028 affects the following packages: com.vaadin:vaadin-bom (Maven), com.vaadin:vaadin-bom (Maven), com.vaadin:vaadin-server (Maven), com.vaadin:vaadin-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-25028?

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.

How do I detect CVE-2019-25028 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-25028 if there is no patch (or I can't update yet)?

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.

Is CVE-2019-25028 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-25028 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-25028?

CVE-2019-25028 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-25028?

CVE-2019-25028 is classified as CWE-80 (CWE-80), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-25028 published, and has it been updated?

CVE-2019-25028 was published on April 23, 2021 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2019-25028 — vaadin-bom

MEDIUMFix: vaadin/framework#11644

CVE-2019-25028 is a medium-severity (CVSS 6.1) CWE-80 vulnerability in com.vaadin:vaadin-bom. A fix is available for com.vaadin:vaadin-bom — see the affected versions and patch details below.

Stored cross-site scripting in Grid component in Vaadin 7 and 8

Also known asGHSA-q74r-4xw3-ppx9

Published

Apr 23, 2021

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

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

4 pkgs affected

☕com.vaadin:vaadin-bom☕com.vaadin:vaadin-bom☕com.vaadin:vaadin-server☕com.vaadin:vaadin-server

Real-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.

https://vaadin.com/security/cve-2019-25028

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:vaadin-bom`	≥ 7.4.0&&< 7.7.20	7.7.20`com.vaadin:vaadin-bom:7.7.20`
☕Maven	`com.vaadin:vaadin-bom`	≥ 8.0.0&&< 8.8.5	8.8.5`com.vaadin:vaadin-bom:8.8.5`
☕Maven	`com.vaadin:vaadin-server`	≥ 7.4.0&&< 7.7.20	7.7.20`com.vaadin:vaadin-server:7.7.20`
☕Maven	`com.vaadin:vaadin-server`	≥ 8.0.0&&< 8.8.5	8.8.5`com.vaadin:vaadin-server:8.8.5`

Affected Products

1 product · 2 configurations

Application

vaadinvaadin

≥ 8.0.0 && < 8.8.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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

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. - https://vaadin.com/security/cve-2019-25028

O3 Security · Impact-Aware SCA

Is CVE-2019-25028 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-80CWE-80 CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

framework

5.6/10

Maintained6/10

Code-Review10/10

Branch-Protection8/10

Assessed Nov 2, 2026

Timeline

Disclosed

Apr 23, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2019-25028

GHSA-q74r-4xw3-ppx9

References

Advisoryvaadin.com · cve 2019 25028 Advisorynvd.nist.gov · CVE 2019 25028 Fixgithub.com Fixgithub.com Webgithub.com · GHSA q74r 4xw3 ppx9

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting vaadin-bom are rated as high or higher (top: high).

CVE-2021-33611GHSA-jfmf-w293-8xr8GHSA-hw7r-qrhp-5pffCVE-2021-33604CVE-2021-31412CVE-2021-31411CVE-2021-31408CVE-2021-31405

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026