CVE-2026-76349 is a vulnerability in Splunk Enterprise versions prior to 10.2.6, 10.0.9, and 9.4.14. It allows an unauthenticated attacker to trick an authenticated user into executing arbitrary Search Processing Language (SPL) commands via a crafted Splunk Web link. This occurs because Splunk Web improperly handles form token values from URLs, failing to neutralize special elements that can alter query logic. Exploitation requires user interaction through phishing. The vulnerability is fixed in Splunk Enterprise 10.2.6 and later versions.
CVE-2026-76331 is a high-severity vulnerability in Splunk Enterprise that affects versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows users without admin or power roles to inject Search Processing Language (SPL) into saved-search dispatch requests due to improper validation of caller-supplied time values. This can lead to unauthorized access to data and compromise system integrity.
CVE-2026-76329 is a vulnerability in Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows an unauthenticated attacker to trick an admin user into opening a crafted Monitoring Console link that executes attacker-controlled Search Processing Language (SPL) commands with the admin's permissions. This can lead to exposure of data accessible to the admin or modification of lookup data. Exploitation requires phishing the admin user to open the malicious link. The vulnerability arises from insufficient validation of data used in dashboard searches within the Monitoring Console.
CVE-2026-76327 is a vulnerability in Splunk Enterprise and Splunk Secure Gateway versions prior to specified fixed releases. It allows an unauthenticated attacker to trick an admin or sc_admin user into opening a crafted URL that executes arbitrary Search Processing Language (SPL) commands with the victim's permissions. This occurs because dashboard searches do not properly neutralize user-supplied input, enabling modification of query logic. Exploitation requires phishing the targeted user to initiate the request in their browser. The vulnerability can expose data accessible to the user and affect search results or lookup data.
CVE-2026-76320 is a vulnerability in Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, and 9.4.14. It allows an unauthenticated attacker to cause an authenticated user to execute arbitrary Search Processing Language (SPL) queries via the Event Type Builder. This occurs because the Event Type Builder improperly handles special elements in queries, retaining SPL-affecting values from cross-site request inputs. Exploitation requires phishing the authenticated user to initiate a crafted request in their browser. The vulnerability could expose sensitive data and stored credentials. The CVSS score is 5.9 (medium severity).
CVE-2026-76254 is a high-severity vulnerability in Splunk Enterprise versions prior to 10.4.2, 10.2.6, 10.0.9, 9.4.14, and 9.3.14. It allows an unauthenticated attacker to cause another user to dispatch arbitrary Search Processing Language (SPL) pipelines with that user's privileges via Dataset Explorer. This occurs because Dataset Explorer fails to properly validate or escape dataset names and does not apply SPL safeguards for risky commands. Exploitation requires phishing the victim to open a crafted link, so the attacker cannot exploit it at will. The vulnerability impacts data confidentiality, integrity, and system availability.
CVE-2026-62681 is a critical code injection vulnerability in orval versions prior to 8.21.0. The issue arises because unescaped backticks in OpenAPI paths are directly embedded into JavaScript template literals used for generating request URLs in clients like axios, fetch, react-query, and SWR. This flaw allows attacker-controlled JavaScript code to be executed in environments where the generated code runs, such as developer machines, CI pipelines, test environments, or applications. The vulnerability is fixed in version 8.21.0.
Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site's content. Prior to 1.0.0-rc.16, the Grav API plugin JwtAuthenticator::extractBearerToken() accepts a JWT from the token URL query parameter on every /api/v1 route, including state-changing endpoints. Request URLs consequently expose valid access tokens through Apache, proxy, and CDN logs, browser history, and Referer headers, allowing a party with access to those records to reuse the token with the owner's API privileges. This issue is fixed in version 1.0.0-rc.16.
HumHub Community Edition 1.18.4 has a reflected cross-site scripting (XSS) vulnerability in the Space membership-request workflow. This flaw allows an attacker to inject malicious JavaScript via the options query-string parameter in the membership request form URL. When an authenticated non-member submits the form, the server responds with attacker-controlled script code, potentially compromising the user's session or data.
A vulnerability in aardvark-dns allows a specially crafted TCP DNS query followed by a connection reset to trigger an infinite error loop, causing 100% CPU usage and denial of service. This component is accessible only via internal Podman networks, so exploitation requires local container network access. Mitigation involves disabling DNS in Podman networks if container name resolution is not needed.
An unauthenticated SQL injection vulnerability exists in the yootheme.com Zoo extension for Joomla versions 1.0.0 through 4.1.63. The flaw occurs in the ItemController::element() method where the filter_type request parameter is directly interpolated into an SQL query without proper quoting or escaping, allowing attackers to manipulate the query structure.
Joomla Extension - balbooa.com - Pre-auth PHP Code Injection in Balbooa Forms < 2.4.3.2 - The form's optional custom-PHP post-submission handler is executed via eval(). The [URL parameter = X] shortcode is substituted with the raw, unescaped value of a query parameter, letting an unauthenticated attacker inject arbitrary PHP that executes server-side. The CSRF token needed to reach the endpoint is itself disclosed anonymously via a separate task, so it provides no real protection. Exploitability requires the form to have a custom-PHP handler configured (a documented builder feature) referencing that shortcode, and no reCAPTCHA on the submit button.
Pydio Cells 5.0.0 through 5.0.2 returns share-link details to any authenticated user. The REST handler for GET /a/share/link/{Uuid} in idm/share/rest/handler.go reads the workspace UUID from the path, calls LinkById, and writes the result with no authorization step, whereas the sibling handler for GET /a/share/cell/{Uuid} loads the workspace and requires MatchPolicies with ResourcePolicyAction_READ, returning a not-found error so that existence is not disclosed. Nothing compensates further down: GetLinkWorkspace reaches GetOrCreateWorkspace, which issues SearchWorkspace with a query carrying no ResourcePolicyQuery, and PrepareResourcePolicyQuery returns the query unmodified when that field is nil, so the workspace service applies no policy filter. The workspace UUID is not secret, because the unauthenticated public page served for a share link embeds it as START_REPOSITORY. Any account holding a standard user role can therefore submit the UUID and receive the link hash and URL, the owner's user identifier, the hidden share user login, the permission set, the download limit and count, the target users, the expiry, and the password-required flag, while a direct read of the shared node from the same account is refused.
RAGFlow before 0.26.3 contains a server-side request forgery vulnerability in the agent workflow "Invoke" component (agent/component/invoke.py). The component builds an outbound request URL from canvas configuration and runtime template variables and passes it to requests.get, requests.post, or requests.put without calling the shared assert_url_is_safe validator or pinning the resolved address, unlike the crawler, SearXNG, file-upload, and RSS fetch paths. A user who can create or trigger an agent can direct the server to fetch loopback, link-local, and RFC 1918 destinations, including cloud instance metadata endpoints and services co-located on the deployment network, and the response body is returned as the component output. Where an agent is configured to interpolate the chat query into the Invoke URL, the destination is chosen by whoever can send that query.
A vulnerability in GitLab CE/EE versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 allowed unauthenticated users to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling. This issue has been remediated by GitLab.
CVE-2026-74880 is a critical vulnerability in jahlives openssl_encrypt versions before 1.4.0 where refresh tokens are accepted as URL query parameters in keyserver and telemetry server routes. This design allows attackers to extract sensitive tokens from server logs, proxy logs, browser history, and HTTP Referer headers, potentially leading to unauthorized access.
The WC Vendors – WooCommerce Multivendor, WooCommerce Marketplace, Product Vendors plugin for WordPress is vulnerable to generic SQL Injection via the 'status' parameter in all versions up to, and including, 2.7.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with shop manager-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The sanitize_text_field callback strips HTML but leaves SQL metacharacters intact, and wp_magic_quotes slash protection does not apply because WP_REST_Server::serve_request() calls wp_unslash() on GET parameters before the sanitize callback executes.
The Royal Elementor Addons plugin for WordPress is vulnerable to Server-Side Request Forgery in versions up to, and including, 1.7.1064 via the Form Builder widget's 'webhook_url' setting. The widget's render() method persists the attacker-controlled URL into the wpr_webhook_url_{widget_id} option on every render (including a Contributor previewing their own draft), and the wpr_form_builder_webhook AJAX handler — registered for both authenticated and unauthenticated callers — reads that option and dispatches the outbound request via the non-safe wp_remote_post(), with no host allowlist, no scheme restriction, and no private/loopback IP filter (the plugin's existing wpr_is_blocked_remote_host / wpr_is_private_or_local_ip helpers are not called on this path). This makes it possible for authenticated attackers, with Contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.
The Query Wrangler plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.5.57 via the 'options' parameter parameter. This is due to missing capability check and nonce verification on the wp_ajax_qw_form_ajax handler, combined with unsanitized attacker-controlled options fully replacing saved query options and being passed directly to call_user_func_array() guarded only by function_exists(). This makes it possible for authenticated attackers, with subscriber-level access and above, to execute code on the server. Exploitation requires only that at least one query row exists in the database, as the query_id is a small enumerable integer with no further access control.
The KiviCare – Clinic & Patient Management System (EHR) plugin for WordPress is vulnerable to generic SQL Injection via the 'searchTerm' parameter in all versions up to, and including, 4.5.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a KiviCare custom role with the 'settings_view' permission (e.g., Doctor or Receptionist), meaning standard WordPress subscribers cannot exploit this without a KiviCare-assigned role.