Security readout for executives and security teams
Plain-English summary
This issue affects older Vaadin 7 and 8 applications using the Grid component. A sanitization gap could let an attacker store JavaScript that later runs in another user’s browser. Business risk is mainly account/session exposure or data tampering inside the affected application, not server takeover.
Executive priority
Treat as a moderate-priority remediation for legacy Vaadin applications, especially business portals or admin tools with untrusted data entry. It should be fixed in normal patch cycles unless exposed to broad external users.
Technical view
CVE-2019-25028 is stored cross-site scripting in Vaadin Grid caused by missing variable sanitization in com.vaadin:vaadin-server 7.4.0-7.7.19 and 8.0.0-8.8.4. It is CWE-80 with CVSS 3.1 score 5.4: network reachable, high complexity, changed scope, low confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to Java web applications that still depend on affected Vaadin 7 or 8 vaadin-server versions and render attacker-controlled or user-controlled content in Grid components.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The vector is unspecified, so treat exploitation evidence as incomplete. Stored XSS generally requires malicious content to be saved and later viewed in the vulnerable UI.
Researcher notes
The public bundle names affected ranges and component but says the injection vector is unspecified. Avoid assuming exploit mechanics. Validation should center on dependency confirmation, Grid data-flow review, and checking whether the vendor advisory maps to the deployed framework version.
Mitigation direction
- Inventory Vaadin and com.vaadin:vaadin-server dependency versions across applications.
- Move affected applications outside Vaadin 7.4.0-7.7.19 and 8.0.0-8.8.4 ranges.
- Follow Vaadin’s advisory and linked framework pull requests for authoritative fix guidance.
- Prioritize applications where Grid displays user-submitted or externally sourced content.
- Apply compensating input validation and output encoding where upgrade timing is constrained.
Validation and detection
- Check Maven or Gradle manifests for com.vaadin:vaadin-server affected versions.
- Identify Grid views that display user-controlled, imported, or integration-sourced data.
- Confirm deployed artifacts match remediated dependency versions, not only source manifests.
- Review vendor advisory details before signing off remediation.
- Look for historical reports of suspicious script execution in affected Vaadin UI paths.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-80: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-25028 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N2.22.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://vaadin.com/security/cve-2019-25028CVE reference · x_refsource_MISC
- https://github.com/vaadin/framework/pull/11644CVE reference · x_refsource_MISC
- https://github.com/vaadin/framework/pull/11645CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.