Vulnerabilities exploitable today
365,633in 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,682
New KEV · 24H0
Exploit Today ≥ 701,626
Distribution · last window
- Critical2,365
- High10,105
- Medium4,998
- Low469
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-392296.5 MED15.0%
——4Bolt CMS through 3.7.0 allows SQL Injection in the 'order' parameter of the content listing pages. An authenticated attacker with low-level privileges can exploit this through the OrderDirective component. This allows for the extraction of sensitive information37dCVE-2024-49296—15.0%
——4——CVE-2024-68325.9 MED15.0%
——4The account locking mechanism fails to trigger when secondary user stores are inaccessible. The software does not maintain a consistent state for account locking if it cannot reach all configured user stores, allowing an attacker to repeatedly attempt authentication with invalid credentials without triggering the lockout mechanism for users within active stores.
When the account locking mechanism is bypassed due to the inaccessibility of secondary user stores, users in accessible user stores are left vulnerable to brute force attacks. A malicious actor can exploit this by attempting numerous invalid password combinations against a user account without the expected account lockout consequence.18dCVE-2022-2977—15.0%
——4——CVE-2026-655345.9 MED15.0%
——4Author Cross Site Scripting (XSS) in Custom links in Elementor Image Carousel <= 1.1.1 versions.35dCVE-2025-14882—15.0%
——4——CVE-2025-54077—15.0%
——4——CVE-2020-0522—15.0%
——4——CVE-2024-24826—15.0%
——4——CVE-2026-246285.9 MED15.0%
——4Administrator Cross Site Scripting (XSS) in Photo Gallery by Supsystic <= 1.16.3 versions.35dCVE-2025-60632—15.0%
——4——CVE-2025-49728—15.0%
——4——CVE-2020-24505—15.0%
——4——CVE-2020-0525—15.0%
——4——CVE-2023-52900—15.0%
——4——CVE-2023-28181—15.0%
——4——CVE-2025-61096—15.0%
——4——CVE-2026-655505.9 MED15.0%
——4Shop Manager Cross Site Scripting (XSS) in Tabs <= 2.5 versions.35dCVE-2024-44644—15.0%
——4——CVE-2023-5934—15.0%
——4——CVE-2021-47100—15.0%
——4——CVE-2025-26514—15.0%
——4——CVE-2026-654835.9 MED15.0%
——4Author Cross Site Scripting (XSS) in HashThemes Demo Importer <= 1.4.2 versions.35dCVE-2025-65278—15.0%
——4——CVE-2024-29967—15.0%
——4——CVE-2021-469897.1 HIG15.0%
——4In the Linux kernel, the following vulnerability has been resolved:
hfsplus: prevent corruption in shrinking truncate
I believe there are some issues introduced by commit 31651c607151
("hfsplus: avoid deadlock on file truncation")
HFS+ has extent records which always contains 8 extents. In case the
first extent record in catalog file gets full, new ones are allocated from
extents overflow file.
In case shrinking truncate happens to middle of an extent record which
locates in extents overflow file, the logic in hfsplus_file_truncate() was
changed so that call to hfs_brec_remove() is not guarded any more.
Right action would be just freeing the extents that exceed the new size
inside extent record by calling hfsplus_free_extents(), and then check if
the whole extent record should be removed. However since the guard
(blk_cnt > start) is now after the call to hfs_brec_remove(), this has
unfortunate effect that the last matching extent record is removed
unconditionally.
To reproduce this issue, create a file which has at least 10 extents, and
then perform shrinking truncate into middle of the last extent record, so
that the number of remaining extents is not under or divisible by 8. This
causes the last extent record (8 extents) to be removed totally instead of
truncating into middle of it. Thus this causes corruption, and lost data.
Fix for this is simply checking if the new truncated end is below the
start of this extent record, making it safe to remove the full extent
record. However call to hfs_brec_remove() can't be moved to it's previous
place since we're dropping ->tree_lock and it can cause a race condition
and the cached info being invalidated possibly corrupting the node data.
Another issue is related to this one. When entering into the block
(blk_cnt > start) we are not holding the ->tree_lock. We break out from
the loop not holding the lock, but hfs_find_exit() does unlock it. Not
sure if it's possible for someone else to take the lock under our feet,
but it can cause hard to debug errors and premature unlocking. Even if
there's no real risk of it, the locking should still always be kept in
balance. Thus taking the lock now just before the check.24dCVE-2023-52569—15.0%
——4——CVE-2023-52821—15.0%
——4——CVE-2024-34623—15.0%
——4——CVE-2024-44658—15.0%
——4——CVE-2025-51825—15.0%
——4——CVE-2025-59870—15.0%
——4——CVE-2020-26267—15.0%
——4——CVE-2024-26847—15.0%
——4——CVE-2026-188496.8 MED15.0%
——4IBM OpenBMC FW1060.00 through FW1060.80 is affected by a vulnerability in the BMC firmware update process. An attacker with authenticated administrator-level access to the BMC can, under specific conditions, execute arbitrary code, resulting in a confidentiality, integrity, and availability impact.6dCVE-2026-23193—15.0%
——4——CVE-2025-66486—15.0%
——4——CVE-2021-47211—15.0%
——4——CVE-2025-54078—15.0%
——4——CVE-2024-55408—15.0%
——4——