Skip to content
Noroxi
NVD / CVE Program· CNA Vaadin

CVE-2023-25500: Possible information disclosure in Vaadin 10.0.0 to 10.0.23, 11.0.0 to 14.10.1, 15.0.0 to 22.0.28, 23.0.0 to 23.3.13, 24.0.0 to 24.0.6…

MediumCVSS 4.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 17/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.51% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: com.vaadin:flow-server (Maven) 1.0.21, 2.9.3, 23.3.13; com.vaadin:vaadin (Maven) 10.0.24, 14.10.2, 22.1.0.

Low priority for now. Upgrade to com.vaadin:flow-server (Maven) 1.0.21, 2.9.3, 23.3.13; com.vaadin:vaadin (Maven) 10.0.24, 14.10.2, 22.1.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Possible information disclosure in Vaadin 10.0.0 to 10.0.23, 11.0.0 to 14.10.1, 15.0.0 to 22.0.28, 23.0.0 to 23.3.13, 24.0.0 to 24.0.6, 24.1.0.alpha1 to 24.1.0.rc2, resulting in potential information disclosure of class and method names in RPC responses by sending modified requests.

Published
Jun 22, 2023
Updated
Sep 14, 2026
EPSS
0.5% · 44th percentile

Report tools

JSON

Action score

17

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
4.3
CNA · Vaadin
3.5
0.8 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-25500

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for vaadin records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
vaadinvaadin

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.

  • flow flow-server

    • 1.0.0 and later · up to and including 1.0.20affected · maven
    • 1.1.0 and later · up to and including 2.9.2affected · maven
    • 3.0.0 and later · up to and including 9.1.1affected · maven
    • 23.0.0 and later · up to and including 23.3.12affected · maven
    • 24.0.0 and later · up to and including 24.0.8affected · maven
    • 24.1.0.alpha1 and later · up to and including 24.1.0.rc3affected · maven

  • vaadin vaadin

    • 10.0.0 and later · up to and including 10.0.23affected · maven
    • 11.0.0 and later · up to and including 14.10.1affected · maven
    • 15.0.0 and later · up to and including 22.0.28affected · maven
    • 23.0.0 and later · up to and including 23.3.13affected · maven
    • 24.0.0 and later · up to and including 24.0.6affected · maven
    • 24.1.0.alpha1 and later · up to and including 24.1.0.rc2affected · maven
Affected versions · NVD (6)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vaadin vaadin10.0.0 and later · before 10.0.23
  • vaadin vaadin11.0.0 and later · before 14.10.2
  • vaadin vaadin15.0.0 and later · up to 22.0.28 inclusive
  • vaadin vaadin23.0.0 and later · before 23.3.14
  • vaadin vaadin24.0.0 and later · before 24.0.7
  • vaadin vaadin24.1.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavencom.vaadin:flow-serverfrom 1.0.0 · before 1.0.211.0.21
Mavencom.vaadin:flow-serverfrom 1.1.0 · before 2.9.32.9.3
Mavencom.vaadin:flow-serverfrom 23.0.0 · before 23.3.1323.3.13
Mavencom.vaadin:flow-serverfrom 24.0.0 · before 24.0.924.0.9
Mavencom.vaadin:flow-serverfrom 24.1.alpha1 · before 24.1.024.1.0
Mavencom.vaadin:flow-serverfrom 3.0.0 · before 9.1.29.1.2
Mavencom.vaadin:vaadinfrom 10.0.0 · before 10.0.2410.0.24
Mavencom.vaadin:vaadinfrom 11.0.0 · before 14.10.214.10.2
Mavencom.vaadin:vaadinfrom 15.0.0 · before 22.1.022.1.0
Mavencom.vaadin:vaadinfrom 23.0.0 · before 23.3.1423.3.14
Mavencom.vaadin:vaadinfrom 24.0.0 · before 24.0.724.0.7
Mavencom.vaadin:vaadinfrom 24.1.0.alpha1 · before 24.1.024.1.0

Same product

vaadin: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-107588Multiple Vulnerabilities in the Highcharts Library Bundled with Vaadin Charts
    33Monitor
  • CVE-2021-31409Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-19
    31Monitor
  • CVE-2020-36320Regular expression Denial of Service (ReDoS) in EmailValidator class in Vaadin 7
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-29567May 24, 2022 · Possible information disclosure inside TreeGrid component with default data provider
    30Monitor
  • ← EarlierCVE-2023-25499Jun 22, 2023 · Possible information disclosure in non visible components
    26Monitor
  • Later →CVE-2025-9467Sep 4, 2025 · Possibility to bypass file upload validation on the server-side
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:com.vaadin:flow-server1.0.21Package registry (OSV)
Maven:com.vaadin:flow-server2.9.3Package registry (OSV)
Maven:com.vaadin:flow-server23.3.13Package registry (OSV)
Maven:com.vaadin:flow-server24.0.9Package registry (OSV)
Maven:com.vaadin:flow-server24.1.0Package registry (OSV)
Maven:com.vaadin:flow-server9.1.2Package registry (OSV)
Maven:com.vaadin:vaadin10.0.24Package registry (OSV)
Maven:com.vaadin:vaadin14.10.2Package registry (OSV)
Maven:com.vaadin:vaadin22.1.0Package registry (OSV)
Maven:com.vaadin:vaadin23.3.14Package registry (OSV)
Maven:com.vaadin:vaadin24.0.7Package registry (OSV)
Maven:com.vaadin:vaadin24.1.0Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records