Vulnerabilities exploitable today
366,836in 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,685
New KEV · 24H0
Exploit Today ≥ 701,629
Distribution · last window
- Critical2,360
- High9,604
- Medium5,457
- Low531
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-2913—15.7%
——5——CVE-2026-55836.3 MED15.7%
——5A security vulnerability has been detected in PHPGurukul Online Shopping Portal Project 2.1. This affects an unknown part of the file /my-profile.php of the component Parameter Handler. The manipulation of the argument fullname leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.36dCVE-2021-46996—15.7%
——5——CVE-2018-11876—15.7%
——5——CVE-2026-619387.0 HIG15.7%
——5Use after free in Windows Installer allows an authorized attacker to elevate privileges locally.12dCVE-2018-11874—15.7%
——5——CVE-2026-255674.3 MED15.7%
——5WeKan versions prior to 8.19 contain an insecure direct object reference (IDOR) in the card comment creation API. The endpoint accepts an authorId from the request body, allowing an authenticated user to spoof the recorded comment author by supplying another user's identifier.46dCVE-2024-50502—15.7%
——5——CVE-2022-47609—15.7%
——5——CVE-2024-47718—15.7%
——5——CVE-2023-25463—15.7%
——5——CVE-2023-4248—15.7%
——5——CVE-2024-27149—15.7%
——5——CVE-2026-24590—15.7%
——5——CVE-2026-13227—15.7%
——5An Improper Authorization vulnerability exists in ERPNext version <v16.25.0 and <15.115.0 due to insufficient access control in the whitelisted API method erpnext.crm.doctype.prospect.prospect.get_opportunities.
This issue affects ERPNext: before 15.115.0, before 16.26.0.19hCVE-2025-13795—15.7%
——5——CVE-2024-55592—15.7%
——5——CVE-2026-41522—15.7%
——5Iris is a web collaborative platform that helps incident responders share technical details during investigations. Prior to version 2.4.28, DFIR-IRIS exposes an optional GraphQL endpoint at `/graphql` that does not enforce the same authorization checks as the REST API. Any authenticated user can abuse it in three ways: unauthorized IOC read across cases (IDOR), bulk IOC disclosure via `case.iocs`. The `case(caseId: …).iocs` resolver returns IOCs linked to an arbitrary case without verifying the caller has access to that case, and unauthorized case creation. All three are reachable by any authenticated user, regardless of role or case ACL. This is fixed in v2.4.28. The GraphQL blueprint, resolvers, and dependencies (`graphene`, `graphene-sqlalchemy`, `graphql-server[flask]`) were removed entirely, since the feature was not in use. As a workaround, block `/graphql` at the reverse proxy (recommended) or comment out the `graphql_blueprint` import and `register_blueprint` call in `source/app/views.py` and restart.38dCVE-2026-400487.8 HIG15.7%
——5The Camel-PQC FileBasedKeyLifecycleManager class deserializes the contents of `<keyId>.key` files in the configured key directory using java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. The cast to `java.security.KeyPair` is evaluated only after `readObject()` has already returned, so any `readObject()` side effects in the deserialized object run before the type check. An attacker who can write to the key directory used by a Camel application — for example through a path traversal into the directory, misconfigured filesystem permissions on the volume where keys are stored, a compromised key provisioning pipeline, or a symlink attack — can place a crafted serialized Java object that, when deserialized during normal key lifecycle operations, results in arbitrary code execution in the context of the application.
This issue affects Apache Camel: from 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2.
Users are recommended to upgrade to version 4.20.0, which fixes the issue by replacing java.io.ObjectInputStream-based key and metadata storage with standard PKCS#8 (private key) / X.509 SubjectPublicKeyInfo (public key) Base64 JSON encoding. For users on the 4.18.x LTS releases stream, upgrade to 4.18.2.45dCVE-2024-23928—15.7%
——5——CVE-2024-26915—15.7%
——5——CVE-2023-40210—15.7%
——5——CVE-2024-27148—15.7%
——5——CVE-2023-52789—15.7%
——5——CVE-2026-7731—15.7%
——5——CVE-2026-528429.3 CRI15.7%
——5Lightpanda is a headless browser designed for AI and automation. Prior to 0.3.1, Lightpanda searched for @ across the entire URL string instead of only the authority component when computing a page origin, so a URL such as `http://attacker.com/@victim.com/` was fetched from attacker.com but treated as `http://victim.com`, allowing a complete Same-Origin Policy bypass. This issue is fixed in version 0.3.1.45dCVE-2022-28218—15.7%
——5——CVE-2026-333507.5 HIG15.7%
——5LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application that provides data- and project-management for neuroimaging research. Prior to 27.0.3 and 28.0.1, a SQL injection has been identified in some code sections for the MRI feedback popup window of the imaging browser. Attackers can use SQL ingestion to access/alter data on the server. This vulnerability is fixed in 27.0.3 and 28.0.1.35dCVE-2026-7447—15.7%
——5——CVE-2025-8064—15.7%
——5——CVE-2024-7872—15.7%
——5——CVE-2023-39165—15.7%
——5——CVE-2026-613617.0 HIG15.7%
——5Use after free in Windows DHCP Client allows an authorized attacker to execute code locally.16dCVE-2025-27027—15.7%
——5——CVE-2025-66104—15.7%
——5——CVE-2026-387534.9 MED15.7%
——5A use-after-free in the awk_sub() function (editors/awk.c) of Busybox v1.38.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted AWK script.40dCVE-2024-50440—15.7%
——5——CVE-2024-27167—15.7%
——5——CVE-2026-796616.5 MED15.7%
——5Ech0 through 4.5.6 registers the PUT /api/echo/like/:id endpoint on the public router group without authentication or rate limiting. Unauthenticated attackers can increment the fav_count counter of any echo (including private echoes) by supplying its UUID, which can be harvested from the public GET /api/echo/page feed. Repeated requests are accepted without deduplication, each triggering a database write and a four-key cache invalidation, allowing attackers to inflate popularity metrics and amplify load on the database and cache. Fixed in 4.7.3.2dCVE-2023-40202—15.7%
——5——