Vulnerabilities exploitable today
368,208in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,694
New KEV · 24H0
Exploit Today ≥ 701,631
Distribution · last window
- Critical2,147
- High7,679
- Medium5,506
- Low542
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-43151—19.3%
——6——CVE-2025-9798—19.3%
——6——CVE-2025-14591—19.3%
——6——CVE-2024-12855—19.3%
——6——CVE-2026-1952—19.3%
——6——CVE-2026-177365.8 MED19.3%
——6Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)32dCVE-2025-28245—19.3%
——6——CVE-2024-11911—19.3%
——6——CVE-2022-488227.8 HIG19.3%
——6In the Linux kernel, the following vulnerability has been resolved:
usb: f_fs: Fix use-after-free for epfile
Consider a case where ffs_func_eps_disable is called from
ffs_func_disable as part of composition switch and at the
same time ffs_epfile_release get called from userspace.
ffs_epfile_release will free up the read buffer and call
ffs_data_closed which in turn destroys ffs->epfiles and
mark it as NULL. While this was happening the driver has
already initialized the local epfile in ffs_func_eps_disable
which is now freed and waiting to acquire the spinlock. Once
spinlock is acquired the driver proceeds with the stale value
of epfile and tries to free the already freed read buffer
causing use-after-free.
Following is the illustration of the race:
CPU1 CPU2
ffs_func_eps_disable
epfiles (local copy)
ffs_epfile_release
ffs_data_closed
if (last file closed)
ffs_data_reset
ffs_data_clear
ffs_epfiles_destroy
spin_lock
dereference epfiles
Fix this races by taking epfiles local copy & assigning it under
spinlock and if epfiles(local) is null then update it in ffs->epfiles
then finally destroy it.
Extending the scope further from the race, protecting the ep related
structures, and concurrent accesses.31dCVE-2026-3506—19.3%
——6——CVE-2024-24697—19.3%
——6——CVE-2026-1250—19.3%
——6——CVE-2025-60155—19.3%
——6——CVE-2025-60129—19.3%
——6——CVE-2022-44079—19.3%
——6——CVE-2025-10125—19.3%
——6——CVE-2023-29656—19.3%
——6——CVE-2023-0189—19.3%
——6——CVE-2025-11332—19.3%
——6——CVE-2024-48041—19.3%
——6——CVE-2026-84995.3 MED19.3%
——6The Helpfulcrowd Product Reviews plugin for WordPress is vulnerable to Authorization Bypass via PHP Type Juggling in versions up to, and including, 1.2.9. This is due to the `helpfulcrowd_validate_token()` function using a loose comparison operator (`!=`) instead of a strict comparison (`!==`) when validating the `token` parameter, while the corresponding REST route `/wp-json/helpfulcrowd/v1/update-settings` is registered with a `permission_callback` of `__return_true`, making it reachable by unauthenticated users; submitting a JSON boolean `true` as the `token` value causes PHP's loose comparison to evaluate as equal to the non-empty base64-encoded secret string, bypassing the check entirely. This makes it possible for unauthenticated attackers to invoke `helpfulcrowd_settings_endpoint()` and write arbitrary attacker-controlled key-value pairs directly into the `helpfulcrowd_options` WordPress database option via `update_option()` without any sanitization or allowlist filtering, enabling full unauthenticated modification of the plugin's stored configuration.43dCVE-2024-27037—19.3%
——6——CVE-2026-48347.5 HIG19.3%
——6The WP ERP Pro plugin for WordPress is vulnerable to SQL Injection via the 'search_key' parameter in all versions up to, and including, 1.5.1. This is due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.42dCVE-2026-47273—19.3%
——6——CVE-2024-49377—19.3%
——6——CVE-2022-43283—19.3%
——6——CVE-2024-27803—19.3%
——6——CVE-2017-11400—19.3%
——6——CVE-2025-21541—19.3%
——6——CVE-2026-201677.7 HIG19.3%
——6A vulnerability in the web-based management interface of Cisco IoT Field Network Director could allow an authenticated, remote attacker with low privileges to cause a DoS condition on a remotely managed router.
This vulnerability is due to improper error handling. An attacker could exploit this vulnerability by submitting crafted input to the web-based management interface. A successful exploit could allow the attacker to request unauthorized files from a remote router, causing the router to reload and resulting in a DoS condition.65dCVE-2021-3452—19.3%
——6——CVE-2023-38535—19.3%
——6——CVE-2025-50009—19.3%
——6——CVE-2025-60121—19.3%
——6——CVE-2024-27054—19.3%
——6——CVE-2023-50738—19.3%
——6——CVE-2020-36085—19.3%
——6——CVE-2024-40850—19.3%
——6——CVE-2023-24861—19.3%
——6——CVE-2022-43148—19.3%
——6——