How severe is CVE-2020-35217?

CVE-2020-35217 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-35217 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-35217?

CVE-2020-35217 primarily affects Eclipse Vert.x-web. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-35217?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2020-35217 published?

CVE-2020-35217 was published on 2021-01-20 and last updated on 2026-06-17.

CVE-2020-35217

CVE-2020-35217 is a high-severity vulnerability in Eclipse Vert.x-web with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.8
EPSS exploit prediction: 1% (44th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-352
Affected product: Eclipse Vert.x-web
Published: 2021-01-20
Last modified: 2026-06-17

Description

Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.

Frequently asked questions

What is CVE-2020-35217?: Vert.x-Web framework v4.0 milestone 1-4 does not perform a correct CSRF verification. Instead of comparing the CSRF token in the request with the CSRF token in the cookie, it compares the CSRF token in the cookie against a CSRF token that is stored in the session. An attacker does not even need to provide a CSRF token in the request because the framework does not consider it. The cookies are automatically sent by the browser and the verification will always succeed, leading to a successful CSRF attack.
How severe is CVE-2020-35217?: CVE-2020-35217 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-35217 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-35217?: CVE-2020-35217 primarily affects Eclipse Vert.x-web. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-35217?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2020-35217 published?: CVE-2020-35217 was published on 2021-01-20 and last updated on 2026-06-17.

References

https://github.com/vert-x3/vertx-web/pull/1613

Affected products (4)

cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone1:*:*:*:*:*:*
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone2:*:*:*:*:*:*
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone3:*:*:*:*:*:*
cpe:2.3:a:eclipse:vert.x-web:4.0.0:milestone4:*:*:*:*:*:*

More vulnerabilities in Eclipse Vert.x-web

CVE-2026-1002 — Medium (CVSS 5.3): The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the…
CVE-2023-24815 — Medium (CVSS 4.8): Vert.x-Web is a set of building blocks for building web applications in the java programming language. When running…

All CVEs affecting Eclipse Vert.x-web →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

CVE-2025-32642 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in appsbd Vite Coupon vite-coupon allows Remote Code Inclusion.This…
CVE-2025-23922 — Critical (CVSS 10.0): Cross-Site Request Forgery (CSRF) vulnerability in Harsh iSpring Embedder embed-ispring allows Upload a Web Shell to a…
CVE-2017-5145 — Critical (CVSS 10.0): An issue was discovered in Carlo Gavazzi VMU-C EM prior to firmware Version A11_U05, and VMU-C PV prior to firmware…
CVE-2019-25729 — Critical (CVSS 9.8): PDF Signer 3.0 contains a server-side template injection vulnerability that allows unauthenticated attackers to execute…
CVE-2025-48340 — Critical (CVSS 9.8): Cross-Site Request Forgery (CSRF) vulnerability in Danny Vink User Profile Meta Manager user-profile-meta allows…
CVE-2025-2907 — Critical (CVSS 9.8): The Order Delivery Date WordPress plugin before 12.3.1 does not have authorization and CSRF checks when importing…

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →