Skip to content
Fencer Intel
medium 5.7

CVE-2023-25499 json

Possible information disclosure in non visible components

published 3y ago modified 2mo ago also GHSA-5f9v-mv5g-jh5q , EUVD-2023-1700

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

When adding non-visible components to the UI in server side, content is sent to the browser in Vaadin 10.0.0 through 10.0.22, 11.0.0 through 14.10.0, 15.0.0 through 22.0.28, 23.0.0 through 23.3.12, 24.0.0 through 24.0.5 and 24.1.0.alpha1 to 24.1.0.beta1, resulting in potential information disclosure.

Patch / fix

  • maven com.vaadin:vaadin 10.0.23, 14.10.1, 23.3.13, 24.0.6, 24.1.0
  • maven com.vaadin:flow-server 1.0.20, 2.8.10, 9.1.1, 23.3.11, 24.0.8, 24.1.0
  • vaadin flow-server 2.9.1

Is CVE-2023-25499 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven com.vaadin:vaadin
>=10.0.0, <10.0.23
>=11.0.0, <14.10.1
>=23.0.0, <23.3.13
>=24.0.0, <24.0.6
>=24.1.0.alpha1, <24.1.0
10.0.23
14.10.1
23.3.13
24.0.6
24.1.0
maven com.vaadin:flow-server
>=1.0.0, <1.0.20
>=1.1.0, <2.8.10
>=3.0.0, <9.1.1
>=23.0.0, <23.3.11
>=24.0.0, <24.0.8
>=24.1.0.alpha1, <24.1.0
1.0.20
2.8.10
9.1.1
23.3.11
24.0.8
24.1.0

Affected products

  • vaadin vaadin
  • vaadin flow-server

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-201 Insertion of Sensitive Information Into Sent Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.