Vulnerabilities exploitable today
376,337in 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,713
New KEV · 24H0
Exploit Today ≥ 701,646
Distribution · last window
- Critical2,382
- High8,758
- Medium6,800
- Low731
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2006-1284—29.5%
——9——CVE-2011-3638—29.5%
——9——CVE-2024-52967—29.5%
——9——CVE-2013-5740—29.5%
——9——CVE-2017-6267—29.5%
——9——CVE-2026-7819—29.5%
——9——CVE-2025-0953—29.5%
——9——CVE-2025-3319—29.5%
——9——CVE-2026-73374—29.5%
——9A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records.
Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the resulting string was wrapped in markupsafe.Markup. Because Markup marks the generated content as safe, Jinja's automatic HTML escaping was bypassed.
An authenticated user with permissions to create or modify vulnerability records, such as a user holding the vulnerability:create or vulnerability:modify permission, could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.
The malicious value would subsequently be stored as part of the vulnerability record. When another user visited the corresponding public /cve/<id> or /vuln/<id> page, the crafted tag would be rendered as HTML in the viewer's browser. This could result in JavaScript execution in the security context of the Vulnerability-Lookup application.
Successful exploitation could allow an attacker to perform actions in the context of a victim, access information available to the victim's browser session, or modify page content. As the affected vulnerability pages can be accessed publicly, exploitation may affect users who are not authenticated.
The issue was corrected by applying markupsafe.escape() to each reference tag before inserting it into the HTML badge markup, while retaining Markup only for the static HTML scaffolding.23dCVE-2025-2239—29.5%
——9——CVE-2024-24459—29.5%
——9——CVE-2026-133927.2 HIG29.5%
——9The ElementsKit Elementor Addons WordPress plugin before 3.10.01 does not prevent a custom-widget definition saved by a user with administrative capabilities from being written verbatim into a generated PHP file that the ElementsKit Elementor Addons WordPress plugin before 3.10.01 subsequently executes, allowing arbitrary PHP code to run on the server; on a multisite network this lets a non-super subsite Administrator, who is otherwise denied code/file editing, reach host-level code execution beyond the privileges the network grants them.23dCVE-2025-9647—29.5%
——9——CVE-2025-15210—29.5%
——9——CVE-2012-5658—29.5%
——9——CVE-2013-4161—29.5%
——9——CVE-2025-50229—29.5%
——9——CVE-2025-12298—29.5%
——9——CVE-1999-1382—29.5%
——9——CVE-2025-42878—29.5%
——9——CVE-2024-48448—29.5%
——9——CVE-2026-44011—29.5%
——9——CVE-2025-60540—29.5%
——9——CVE-2024-29813—29.5%
——9——CVE-2026-85586—29.5%
——9phpMyFAQ versions before 4.1.8 fail to validate CAPTCHA when the store parameter is set to 'now' in question submission requests. Unauthenticated attackers can bypass CAPTCHA protection and submit unlimited questions directly, causing database pollution and triggering outgoing mail notifications.8dCVE-2024-29768—29.5%
——9——CVE-2023-32061—29.5%
——9——CVE-2022-43949—29.5%
——9——CVE-2025-47943—29.5%
——9——CVE-2024-33639—29.5%
——9——CVE-2024-29816—29.5%
——9——CVE-2026-724387.5 HIG29.5%
——9In the Linux kernel, the following vulnerability has been resolved:
md/raid10: fix writes_pending and barrier reference leaks on discard failures
raid10_make_request() acquires a writes_pending reference with
md_write_start() before calling raid10_handle_discard(). Several failure
paths in raid10_handle_discard() complete the bio and return without
releasing the corresponding reference, causing md_write_end() to be
skipped.
Call md_write_end() before returning from these failure paths to keep
writes_pending accounting balanced.
Additionally, discard split allocation failures can occur after
wait_barrier() succeeds. Those paths return without calling
allow_barrier(), leaking the associated barrier reference.
Release the barrier before returning from those paths.32dCVE-2020-5833—29.5%
——9——CVE-2025-13244—29.5%
——9——CVE-2024-20377—29.5%
——9——CVE-2024-30452—29.5%
——9——CVE-2025-10374—29.5%
——9——CVE-2026-760198.1 HIG29.5%
——9Incorrect authorization in Workers in Google Chrome prior to 151.0.7922.173 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)24dCVE-2024-1634—29.5%
——9——CVE-2014-1257—29.5%
——9——