Vulnerabilidades explotables hoy
419,453en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,790
Nuevos KEV · 24H0
Exploit Today ≥ 701,719
Distribución · última ventana
- Crítico4,594
- Alto17,885
- Medio17,958
- Bajo1,946
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-865864.2 MED—
——0Certain EZVIZ devices are affected by a replay attack vulnerability (CWE-294). An attacker may intercept communication traffic and replay specific control commands, causing the device to execute unauthorized operations.2dCVE-2026-1336993.1 BAJ—
——0free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability because sendPDUSessionEstablishmentAccept returns early without calling RemoveSMContextFromAllNF on failures. Authenticated UEs repeatedly establishing PDU sessions during NRF or AMF failures leak SM contexts, UE IP addresses and TEIDs, exhausting the DNN IP pool.2dCVE-2026-865875.3 MED—
——0Certain EZVIZ devices are affected by an improper certificate validation issue (CWE-295). An attacker may intercept communication traffic to conduct a man-in-the-middle attack.1dCVE-2026-1267168.1 ALT—
——0The Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_entry function in all versions up to, and including, 1.7.9 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The attacker-supplied path is stored via the unauthenticated form submission endpoint, but the actual file deletion only occurs when an administrator subsequently deletes the stored entry — a routine housekeeping action that serves as the detonation trigger. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.2dCVE-2026-1217907.2 ALT—
——0The CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[].courier_code, data[].tracking_number (plus pp_sign for the auth bypass)' parameter in all versions up to, and including, 4.6.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The authentication bypass is reachable only when the parcelpanel_api_key WordPress option is non-empty, which occurs automatically once an admin has opened or connected the ParcelPanel admin page; at that point any unauthenticated attacker can bypass the sole access gate by supplying a JSON boolean true as pp_sign, which PHP's loose == operator coerces to true when compared against the non-empty md5 hex string.2dCVE-2026-1290739.8 CRÍ—
——0Authentication Bypass Using an Alternate Path or Channel vulnerability in miniOrange miniorange otp verification miniorange-otp-verification allows Authentication Abuse.This issue affects miniorange otp verification: from n/a through 5.6.1.2dCVE-2026-132660——
——0In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a superuser but do not set a safe search_path. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the intended ones, and so run arbitrary SQL with superuser privileges. Temporary objects can be used for this on every supported PostgreSQL version, and objects in the public schema on PostgreSQL 14 backends and backends upgraded from PostgreSQL 14.
From PEM 10.6.1, these functions run with a fixed search_path.1dCVE-2026-133661——
——0FlowIntel contains multiple authorization and credential management vulnerabilities affecting connector instances, MISP helper tools, and case templates.
- Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data.
- Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access.
- Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints.
- Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication.
These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts.
Affected versions: < 4.1.02dCVE-2026-133648——
——0Flowintel disabled TLS certificate verification for all MISP API connections and used unverified SSL contexts for IMAP and SMTP STARTTLS mail connections. This allowed an on-path (man-in-the-middle) attacker positioned between Flowintel and its MISP or mail servers to impersonate the remote server and intercept sensitive data.
Affected connections include:
- All MISP HTTPS API calls (event retrieval, attribute search, event creation, connectivity checks, and API validation)
- SMTP STARTTLS connections used for sending email notifications
- IMAP TLS connections used for fetching mail archives and testing connectivity
An attacker who can observe or intercept network traffic between Flowintel and the MISP or mail server could:
- Capture MISP API keys and mail credentials (SMTP/IMAP passwords)
- Read all threat intelligence data exchanged (events, attributes, objects, reports)
- Inject or modify threat intelligence data returned to Flowintel
The vulnerability required no authentication on the part of the attacker and no user interaction; it was exploitable by any party with a network position between Flowintel and its configured MISP or mail endpoints.
Affected versions: Flowintel prior to 4.1.0.1dCVE-2026-132661——
——0In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permissions. A similar issue in pgAdmin 4 was assigned CVE-2024-4215.
From PEM 10.6.1, every authenticated PEM route requires a completed MFA check.2dCVE-2026-1180556.4 MED—
——0The My Calendar – Accessible Event Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event_title' parameter in all versions up to, and including, 3.8.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the plugin's documented permission grant to be applied, which allows Subscriber-level users to add and publish events; once granted, a self-submitted event title containing an entity-encoded payload is auto-published and fires in any visitor's browser upon clicking the event on the public calendar.2dCVE-2026-1336216.3 MED—
——0A flaw has been found in shader-slang slangpy up to 0.43.1. This vulnerability affects the function tinyexr::DecodePixelData in the library external/include/tinyexr.h of the component EXR Image Loader. Executing a manipulation can lead to out-of-bounds read. The attack may be performed from remote.2dCVE-2026-1250858.8 ALT—
——0The Nexter Extension – Security, Performance, Code Snippets & Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 4.9.0 This is due to the role_switcher_to_view_admin_as() function handling the `reset-view` branch without a capability check or nonce when the caller's own login is supplied, combined with an incomplete cleanup hook (maybe_prevent_switchback_to_administrator) that exits early when the user's current roles equal the stored view role and that is never triggered when WordPress core's WP_User::set_role() short-circuits because the account already has only the target role. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to Administrator.1dCVE-2026-1336296.3 MED—
——0A vulnerability was determined in Sunnet CTMS up to 10.11. Impacted is an unknown function of the file /cltcms/api/external-training/ext-course of the component External Training Application Form Feature. This manipulation of the argument memberids causes improper control of resource identifiers. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.2dCVE-2026-133838——
——0FlowIntel contains an authorization bypass that allows non-approver case members to modify restricted tasks (those in Requested, Rejected, or Request Review status) through several indirect code paths that lacked the required approver permission check.
Affected operations include:
- Self-unassignment from a restricted task
- Reordering tasks, including indirectly moving restricted sibling tasks
- Linking or unlinking MISP objects and attributes to/from restricted tasks
- Creating MISP objects or standalone attributes with task IDs referencing restricted tasks
- Deleting MISP objects or attributes that are linked to restricted tasks
- Executing modules on restricted tasks
A user with case member access (but without Admin, Case Admin, or Queue Admin privileges) could exploit these paths to alter the state of tasks that are supposed to be locked pending approval, effectively bypassing the intended approval workflow and potentially manipulating associated MISP data.
Affected versions: FlowIntel prior to 4.1.02dCVE-2026-124767——
——0Authorization bypass in the creation of projects in XOneManager 3.8.3.0. The server processes POST requests to ‘/xmanagercore/api/Project/ConvertBDToProject/’ without verifying the administrative role. An authenticated user with basic privileges can create a project and execute SQL queries on the linked database from that project.1dCVE-2026-1317615.3 MED—
——0Missing Authorization vulnerability in Magepeople inc. Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking and Rental Manager: from n/a through 2.8.5.1dCVE-2026-1336015.3 MED—
——0A vulnerability was found in hiparker opsli-boot up to 2.2.1. This affects the function getInputStream of the file opsli-plugins/opsli-plugins-waf/src/main/java/org/opsli/plugins/waf/servlet/WafHttpServletRequestWrapper.java of the component WAF Plugin. The manipulation results in denial of service. The attack can be executed remotely.2dCVE-2026-1335787.3 ALT—
——0A vulnerability was detected in itsourcecode Banking Management System 1.0. This impacts an unknown function of the file manage_donation.php of the component Donor Management. The manipulation of the argument ID results in sql injection. The attack may be performed from remote. The exploit is now public and may be used.2dCVE-2026-133843——
——0flowintel contains a vulnerability in the MISP correlation feature that allows unauthorized disclosure of case identifiers.
The application failed to enforce proper access controls when generating correlation lists for MISP attributes. Specifically, the system did not verify whether the requesting user had permission to view the source case or the matching cases returned in the correlation results. This lack of authorization checks allowed authenticated users to potentially discover the existence of cases they do not have access to, leading to information disclosure.
The vulnerability affects the following components:
- Case correlation logic
- API endpoints for retrieving correlation attributes
- MISP object handling
Affected versions: < 4.1.02dCVE-2026-51239——
——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.114dCVE-2026-133850——
——0flowintel contains an authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient's current access rights to that case before generating or displaying the notification.
As a result, a user who previously had access to a private case and later had that access revoked can still:
- Receive recurring reminder notifications containing case-related content.
- View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case.
The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time.
Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch.
Affected versions: flowintel prior to 4.1.0.2dCVE-2026-133848——
——0flowintel contains an authorization flaw in its user deletion functionality. Organization-scoped administrators (org admins) are able to delete platform-level administrator accounts through both the browser-based admin interface and the REST API.
The existing authorization logic verified that an org admin could only target users within their own organization, but it did not enforce the privilege hierarchy between organization admins and platform admins. As a result, an authenticated org admin could issue a deletion request against any platform-admin account belonging to the same organization, causing the target account, its sessions, and related records to be permanently removed.
Impact:
- Loss of platform-level administrative oversight
- Potential disruption of platform-wide management functions
- Removal of higher-privilege accounts that should be protected from lower-privilege roles
Affected versions: flowintel prior to 4.1.01dCVE-2026-23690——
——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.37dCVE-2026-133853——
——0FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request.
Preconditions:
- An authenticated user with access to the chatbot interface.
- Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment.
Impact:
- A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases).
- A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential.
- The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface.
Affected versions: FlowIntel prior to 4.1.0.2dCVE-2026-1290445.4 MED—
——0Missing Authorization vulnerability in Brainstorm Force Starter Templates astra-sites allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Starter Templates: from n/a through 4.7.11.2dCVE-2026-133854——
——0flowintel contains a vulnerability in the case and task classification usage endpoints that allows authenticated users to view classification data associated with cases they do not have permission to access.
The affected endpoints, which provide lists of used taxonomies, tags, galaxies, clusters, and custom tags, did not properly enforce object-level access controls. While the endpoints required authentication, they failed to filter the returned data based on the requesting user's visibility permissions for the underlying cases. This allowed any authenticated user to enumerate classification usage across all cases, including private or restricted cases belonging to other organizations or users.
This issue could lead to the disclosure of sensitive information, such as the existence of specific cases, the types of threats or indicators associated with them, and the relationships between different classification elements, potentially aiding an attacker in reconnaissance or targeting.
Affected versions: < 4.1.02dCVE-2026-1222447.7 ALT—
——0Budibase is an open-source low-code platform. Prior to 3.50.0, a BASIC application user, or an unauthenticated visitor to a public write form, can store markup in a shared external datasource that a builder or administrator later evaluates in any Handlebars binding Preview that surfaces the value, including the Data-section Formula column editor or any binding drawer. jsonFormatter.format() in packages/frontend-core/src/utils/jsonFormatter.ts leaves raw strings and object keys unescaped, while packages/builder/src/components/common/bindings/EvaluationSidePanel.svelte inserts the formatted result as raw HTML. The Handlebars SafeString path preserves the attacker-controlled value, and the Builder origin lacks a Content-Security-Policy that would block the resulting script. This permits stored script execution in the higher-privileged builder or administrator session rather than the writer's own role, allowing privileged Builder API actions and workspace data access. This issue is fixed in versions 3.50.0 and 4.0.0.1dCVE-2026-1222478.2 ALT—
——0Budibase is an open-source low-code platform. Prior to 3.50.0, the public POST /api/global/users/init endpoint on a self-hosted single-tenant deployment accepts an attacker-controlled tenantId and evaluates checkAnyUserExists() in the selected tenant database instead of the legitimate default tenant. An unauthenticated attacker can select an unused tenant namespace to bypass the one-time initialization guard, causing packages/worker/src/api/controllers/global/users.ts to create a tenant-specific CouchDB database and a global-administrator document without a session or CSRF token. Repeating this operation with unique tenant identifiers can exhaust datastore resources and leave latent privileged records. The created administrator cannot log into the default tenant while multi-tenancy remains disabled, which limits the immediate impact to persistent writes, denial of service, and records that may become usable during later multi-tenant operation or migration. This issue is fixed in versions 3.50.0 and 4.0.0.2dCVE-2026-1322775.3 MED—
——0Inscriptis is a Python library for converting HTML to text. From 2.0.0 until 2.7.6, when the parent is block-level, table_end_handler() in model/tag/table_tag.py writes each sibling table through HtmlElement.write_verbatim_text() in model/html_element.py; Canvas.open_block() leaves the parent padding_inline prefix on the stack, Canvas.close_block() does not remove it, and only Canvas.close_tag() calls prefix.remove_last_prefix(). Each following sibling table therefore carries forward accumulated indentation, making get_text() output grow quadratically and allowing small attacker-controlled HTML to exhaust memory in applications converting it without authentication or user interaction. This issue is fixed in 2.7.6.2dCVE-2026-1338748.1 ALT—
——0Iceburg CRM through 5.0.0 contains an incorrect authorization vulnerability in Module::saveRecord() that allows authenticated users to write to unauthorized modules by prefixing request body keys with another module id. Attackers with write access to one module can submit crafted requests to POST /data/save or PUT /api/crm/{id} to set their role_id to Admin and access administrative data.2dCVE-2026-1331998.5 ALT—
——0Incorrect privilege assignment in the user and group reconciliation logic in AWS ssosync before 2.9.5 might allow an authenticated remote user who is assigned a reused Google Workspace e-mail address or group name to inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity, via automatic synchronization of that Google Workspace account or group.
To remediate this issue, users should upgrade to version 2.9.5 or later.2dCVE-2026-1338765.4 MED—
——0Kartones flask-calendar before commit bfde72e contains a stored cross-site scripting vulnerability because task_details_for_markup returns unescaped content rendered with the |safe filter. Authenticated shared calendar members can store script in task details that executes for other members, letting attackers read and modify their private calendars.1dCVE-2026-1338797.7 ALT—
——0A flaw was found in KubeVirt/containerized-data-importer. When a VirtualMachine with an embedded DataVolumeTemplate carrying the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant, the service-account clone authorization check can be bypassed, allowing a PVC from another namespace to be cloned into the tenant's namespace without the required permissions. This can result in cross-tenant data disclosure.1dCVE-2026-1338784.3 MED—
——0Mattermost versions 11.11.x <= 11.11.1, 11.7.x <= 11.7.14, 11.10.x <= 11.10.4 fail to restrict the broadcast scope of group WebSocket events to sessions permitted to read the group which allows an authenticated user, including guests, to obtain the display name, description, member count and member IDs of non-referenceable groups via the received_group event emitted when a group is created, updated, deleted or restored. Mattermost Advisory ID: MMSA-2026-007312dCVE-2026-238713.5 BAJ—
——0Incomplete validation of external ad-reply URLs in WhatsApp for Android and WhatsApp Business for Android before 2.26.17.4 could have caused a target's device to reveal its IP information to an attacker if an attacker sent media from an attacker-controlled URL when a crafted Click to WhatsApp ad-reply message was rendered and displayed in a message thread. This issue may have been abused in conjunction with specific spam messages.1dCVE-2026-826758.1 ALT—
——0The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to donor account account takeover in all versions up to, and including, 4.17.0. This is due to the plugin not properly validating a donor's identity prior to updating the password of a linked WordPress account. The donation receipt processes an attacker-controlled first name through the V3 template engine and then reprocesses the result through the legacy `{meta_donor_*}` engine, which can disclose the donor's email-access bearer token. The donor-dashboard password endpoint accepts that token by itself and calls `wp_set_password()` for the WordPress user linked to the donor. This makes it possible for unauthenticated attackers to reset the password of any WordPress account linked to a GiveWP donor record and gain access to that account. If the linked account is an administrator, the attacker can achieve full site compromise and remote code execution through standard administrator functionality. A published GiveWP form with a usable gateway, enabled donor email access (enabled by default), knowledge of the donor email address, and an account already linked to the targeted donor record are required. NOTE: This vulnerability can be chained with CVE-2026-82676 to satisfy the administrator donor pre-requisite for a targeted administrator user attack.1dCVE-2026-826764.3 MED—
——0The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.16.7.2. This is due to missing nonce validation on the `give_render_donor_view()` function. This makes it possible for unauthenticated attackers to reassign an arbitrary GiveWP donor record to an arbitrary WordPress user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The resulting association changes donor-account ownership and can satisfy the linked-donor precondition for a separately tracked account-takeover vulnerability (CVE-2026-82675).2dCVE-2026-1041854.3 MED—
——0LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the HTML bookmark import action in app/Actions/ImportHtmlBookmarks.php uses the global Link::whereUrl() lookup instead of restricting duplicate detection to the importing user. An authenticated user can submit a chosen URL and distinguish the skipped response count from the queued count to learn whether any account has saved that URL, including as a PRIVATE bookmark. The oracle reveals URL existence but does not directly return the bookmark contents or owner. This issue is fixed in version 2.6.0.1dCVE-2026-1041847.1 ALT—
——0LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, LinkController::update() in app/Http/Controllers/API/LinkController.php passes $request->all() to the repository update method even though user_id is fillable and is not an allowed field in the validated update request. An authenticated API user who is authorized to update a link can therefore assign an arbitrary or nonexistent user_id, transferring the link into another user's bookmark collection or orphaning it from any real account. The web update controller is unaffected because it passes only validated fields. This issue is fixed in version 2.6.0.2d