CVE-2026-7170 is a stored cross-site scripting (XSS) vulnerability in the TPVEnlanube Cloud Web application. It affects the 'vendor_store_name' parameter in the '/administrator/index.php?pshop_mode=admin&page=store.store_add&option=com_virtuemart&vendor_id=[ID]' endpoint. An authenticated attacker could exploit this flaw to inject malicious scripts that execute in users' browsers. The vulnerability has a medium severity rating with a CVSS 4.8 score. No patch or remediation information is currently provided.
CVE-2026-97531 is a vulnerability related to the SCSI qla2xxx driver, specifically involving skipping a vport under deletion during report ID acquisition. The information provided is minimal and does not describe the technical details or impact of the vulnerability. The affected versions are exactly 3.0 and 4.0. No CVSS score or exploit information is available.
CVE-2026-97598 is a published vulnerability related to IPv4's fib (Forwarding Information Base) automatic table ID allocation in Microsoft software versions 3.0 and 4.0. No detailed technical or impact information is provided in the available data.
A vulnerability has been found in Krayin laravel-crm up to 2.2.5. The impacted element is the function Storage::download of the file packages/Webkul/Admin/src/Config/acl.php of the component attachment-download Endpoint. The manipulation of the argument ID leads to improper control of resource identifiers. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.2.6 is sufficient to resolve this issue. The identifier of the patch is 13d6988cda8d69ece45ee1890effc90a7f21cdc1. It is suggested to upgrade the affected component.
obot versions before 0.21.1 contain an authorization bypass vulnerability in the /mcp-connect endpoint. This flaw allows any authenticated user who knows a server ID to connect to restricted MCP servers without proper access control enforcement. Exploiting this issue enables attackers to access and manipulate sensitive backend systems via MCP tool calls using stored OAuth credentials. The vulnerability has a critical severity with a CVSS 4.0 score of 9.3.
Fleet before 4.89.0 contains an SQL injection vulnerability in the activity list endpoints (GET /api/v1/fleet/activities and GET /api/v1/fleet/hosts/{id}/activities). The deprecated cursor-pagination helper appendListOptionsWithCursorToSQL interpolated the caller-supplied sort/order key into the SQL ORDER BY clause without an allowlist, so an authenticated user with read access to Activity could order results by arbitrary columns. The impact is read-only and bounded to columns on the activity_past table that are not otherwise returned in these responses (e.g. details), allowing their values to be inferred through the resulting sort order; there is no write access, privilege escalation, or reachability of node_key or other host-join columns through these endpoints. Fixed in 4.89.0, which removes the deprecated helper and passes the sort column through SanitizeColumn.
Parse Server versions >=8.0.2 <8.6.91 and >=9.0.0 <9.10.1-alpha.10 have an improper authentication vulnerability in their code-based authentication adapters. These adapters do not verify the client's authorization code with the external provider during login when authentication data is supplied with username and password. This allows a low-privileged authenticated user to link an arbitrary, unverified external provider identity to their account, potentially spoofing trusted identities. Additionally, attackers can pre-hijack accounts by claiming a provider ID before the legitimate user links it. Versions 8.6.91 and 9.10.1-alpha.10 fix this by verifying credentials on login and rejecting already linked provider IDs. Disabling affected adapters is a recommended workaround.
CVE-2026-100860 affects heym versions before 0.0.105. The vulnerability arises because the software does not properly handle failed credential authorization lookups in its Redis workflow node. When a credential ID is invalid, unauthorized, or has an empty configuration, the node falls back to connecting to a local Redis instance on localhost:6379 without authentication, potentially exposing Redis data or functionality. The impact depends on deployment specifics; for example, the default docker-compose setup does not include Redis, resulting only in connection errors rather than data exposure.
The Groups – Memberships and Access Control plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.6.0. This is due to the groups_join() function deriving group-join eligibility from the ambient post's author capabilities via the global $post->post_author rather than from the currently authenticated user's own capabilities, while simultaneously minting and returning a valid groups-join-data hash and WordPress nonce for the caller in the same response — eliminating all authorization barriers to self-enrollment. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enroll themselves into any group including privileged groups carrying the groups_admin_groups capability, and to subsequently create and join a group containing every registered WordPress capability, effectively escalating their privileges to Administrator. Exploitation requires the attacker to supply an Administrator-authored post ID via the post_ID parameter of the authenticated wp_ajax_parse_media_shortcode handler in order to establish the privileged ambient post context used by the flawed authorization check.
Froxlor through 2.3.10 stores only a numeric user ID in remembered-2FA tokens (panel_2fa_tokens) without recording the account namespace, and the remembered-token lookup during login is not constrained to the customer or administrator account type. Because customer and administrator IDs are allocated from separate namespaces, a remembered-2FA token legitimately issued to a customer with a given ID also matches an administrator with the same ID. An attacker who controls a customer account with a colliding ID, holds a valid remembered-2FA cookie for it, and already knows the target administrator's password can bypass the administrator's TOTP second factor and obtain an authenticated administrator session. This is a second-factor bypass only; it does not defeat password authentication. Fixed in 2.3.11.
vLLM before 0.29.0 accepts user-controlled stop_token_ids on the OpenAI-compatible POST /v1/completions and POST /v1/chat/completions endpoints but validates only that the values are integers, not that each token id is within the model vocabulary/logits range. When min_tokens > 0, the stop token ids are used as logits indices to suppress stop tokens, so an out-of-range id reaches a CUDA indexing operation (index_put_) and triggers a device-side assertion. An authenticated API user can send a single malformed completion request that returns 500 Internal Server Error and puts EngineCore into a fatal state, causing subsequent requests to fail until the service is restarted (denial of service).
Parse Server is an open source backend server. In versions prior to 8.6.90 and in versions from 9.0.0 prior to 9.10.1-alpha.9, the device token deduplication logic for installation records does not validate the type of client-supplied installation fields before using them to build database queries. An unauthenticated remote attacker who knows only the public application ID can submit non-string values in these fields to inject query operators, causing the deduplication cleanup — which runs with elevated privileges before class-level permissions are evaluated — to delete every device registration in the application or an attacker-chosen subset of them. No account, session token, master key, or user interaction is required. Deleted registrations cannot be recovered on the server, so push notifications cannot be delivered until every client re-registers. Any deployment that exposes the REST API to clients and uses push notifications is affected in its default configuration. Versions 8.6.90 and 9.10.1-alpha.9 fix the issue by rejecting non-string values with a client error and by scoping the deduplication cleanup to the calling application. No workaround other than upgrading is available.
Capgo (capgo.app) is affected by an authorization flaw in the app icon update path. The PUT /app/:id endpoint accepts a user-controlled `icon` value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's own image namespace (e.g. org/{owner_org}/{app_id}/...). Updating apps.icon_url fires the on_app_update trigger, whose worker reads record.icon_url and calls cleanStoredImageMetadata(), which runs with service-role credentials (supabaseAdmin()) and downloads and re-uploads the referenced storage object with upsert: true. As a result, an authenticated holder of an app-limited write API key can cause the privileged worker to rewrite an out-of-scope private image object (for example an organization logo) that the key cannot read or write directly under Supabase Storage RLS. All versions are affected; no patched version was available at the time of the advisory.
Flowise through 3.1.4 exposes GET /api/v1/upsert-history/:id and PATCH /api/v1/upsert-history without route-level permission checks, and the backing service performs no workspace or ownership validation. getAllUpsertHistory() returns UpsertHistory rows selected solely by an attacker-supplied chatflowid, and patchDeleteUpsertHistory() deletes rows by an attacker-supplied array of record UUIDs. As a result, any authenticated low-privilege user or valid API key can read or delete document-store upsert history belonging to other users and other workspaces whenever the target chatflowId (which is exposed publicly in /chatbot/<chatflowId> share links) or row ids are known. The retrievable flowData and result fields contain embedding, record-manager and vector-store node configuration, including per-node paramValues. No patched version is available.
Flowise (npm packages `flowise` and `flowise-components`) through 3.1.4 looks up credentials by ID without filtering on the requesting user's workspace (findOneBy({ id: credentialId }) with no workspaceId condition) in several code paths: getAllOpenaiAssistants/getSingleOpenaiAssistant (GET /api/v1/openai-assistants and /api/v1/openai-assistants/:id), uploadFilesToAssistant (POST /api/v1/openai-assistants-file/upload/), deleteAssistant (DELETE /api/v1/assistants/:id, reachable by first importing a poisoned assistant row via POST /api/v1/export-import/import), and the shared helper used by getVoices (GET /api/v1/text-to-speech/voices). An authenticated user of one workspace can supply a credential UUID belonging to another workspace, causing the server to decrypt and use that workspace's OpenAI or ElevenLabs API key on the attacker's behalf. No patched version was available at the time of publication.
CVE-2026-100604 is an incorrect authorization vulnerability in the ClawHub backend where organization-owned skills retain the original publisher's user ID. This flaw allows an authenticated user who originally published a skill to transfer, delete, or restore it even after losing organization privileges. The vulnerability was fixed in revision 8c2de6c506bb4efabe3f0c2ffb8370b9e23d4650, deployed on 2026-09-11. Self-hosted deployments should update to this revision or later. The npm CLI and OpenClaw runtime are not affected.
The Team Members WordPress plugin before 9.3 does not perform any authorization or visibility check in an unauthenticated AJAX action that returns full team member records by ID, allowing unauthenticated attackers to enumerate and disclose details, including email addresses and phone numbers, of team members the administrator has not published publicly.
CVE-2026-98104 is a vulnerability in the Linux kernel's net/sched cls_u32 component where duplicate handles can be created when the node ID pool is exhausted. This occurs because the function gen_new_kid() returns a fallback handle value instead of an error when ID ranges are full, causing handle uniqueness to break. This can lead to removal of live nodes and reuse of handles, potentially causing instability or denial of service. The issue affects configurations with CONFIG_NET_SCHED and CONFIG_CLS_U32 enabled. The vulnerability has a medium severity with no confidentiality or integrity impact but can cause availability issues.
CVE-2026-98110 is a high-severity vulnerability in the Linux kernel's Bluetooth subsystem (btintel). The flaw arises because the firmware ID is handled as a NUL-terminated string, but its actual boundary is defined only by the TLV length. If the firmware ID lacks a NUL terminator, the snprintf() function may read beyond the intended buffer, causing an out-of-bounds read.