A vulnerability in Grafana allows a user with query access to an Azure Monitor data source to trigger server-side request forgery (SSRF) that discloses the Azure access token used by the data source. This issue affects multiple Grafana versions prior to fixed releases and can lead to unauthorized disclosure of sensitive credentials.
AdminNeo versions prior to 5.9.1 have an SQL injection vulnerability in the ClickHouse driver. The vulnerability arises because the idf_escape() function improperly handles escaping by doubling backticks but failing to escape backslashes in SQL identifiers. This flaw allows an attacker to craft a GET request with a column name ending in a backslash in certain parameters, causing the query to be parsed as SQL. The vulnerability requires a logged-in user to open a malicious link and has a low severity rating.
B3log Solo through 4.4.0 contains an SQL injection vulnerability in the console article update API that allows authenticated authors to inject SQL through unvalidated JSON property names. Attackers can send a PUT request to /console/article/ with crafted property names used as UPDATE column names, then read query results back through the updated article.
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260722.0, the GraphQL endpoint accepts query operations over HTTP GET because CSRF prevention is disabled (csrfPrevention: false), placing the complete GraphQL query and its arguments in the request URL. Server and reverse-proxy logs, browser history, and shared caches can retain sensitive filters, marking-restricted identifiers, and investigation search arguments, allowing a person with access to those records to recover legitimate users' query contents. GraphQL mutations are not accepted over GET, and the issue does not permit code execution. This issue is fixed in version 7.260722.0.
Axigen Mail Server 10.3.3.67 through 10.3.3.x, 10.4.42 through 10.4.x, 10.5.29 through 10.5.x, 10.6.x before 10.6.41, and 10.7.x before 10.7.3 contains an unauthenticated denial of service vulnerability caused by uncontrolled recursion when validating query parameter and cookie values with a recursive regular expression engine before authentication in the WebAdmin and WebMail services. Attackers can send a single HTTP request with a query parameter or cookie value of a few thousand characters to exhaust the worker thread stack and crash the server process, taking down SMTP, IMAP, POP3, and web services repeatedly.
A denial-of-service (DoS) vulnerability exists in @sveltejs/kit versions 2.42.0 up to but not including 3.1.1 when using the experimental remote functions flag with the `form`, `query`, or `command` remote functions. A specially crafted request can block the event loop for extended periods during form data parsing, causing application unavailability. This issue is fixed in version 3.1.1.
Weblate 2026.6 through 2026.11.2 contains an information disclosure vulnerability in ChangeManager.last_changes() that exposes workspaces the viewer cannot view by skipping Workspace.can_view() checks site-wide. Anonymous visitors on instances with REQUIRE_LOGIN disabled and only public projects can query /changes/, /api/changes/, or RSS/CSV feeds to obtain hidden workspace names, UUIDs, actions, and timestamps.
visualTicket is vulnerable to information exposure through an error message in the order creation functionality. Because detailed data-layer exceptions are returned to the client instead of being logged server-side only, a remote unauthenticated attacker can submit a valid checkout request with an invalid payment_type value, causing the application to return a detailed SQL/ORM error that discloses the database name, table and column names, query structure, and foreign key constraint name.
This issue was fixed in version 20260817.
Kroki before 0.36.0 contains a server-side request forgery vulnerability in the BlockDiag family of engines that allows unauthenticated attackers to make server requests via node icon and background attributes. Attackers can send crafted diagrams to POST /blockdiag/svg or sibling endpoints to query internal services or cloud metadata and read local image files from the server.
The Give - Peer-to-Peer plugin for WordPress is vulnerable to time-based SQL Injection via the 'sort' parameter in all versions up to, and including, 2.9.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Successful exploitation requires the existence of at least one Peer-to-Peer campaign. This vulnerability can be combined with CVE-2026-82663 to achieve unauthenticated remote code execution.
CVE-2026-126191 is a high-severity Regular Expression Denial of Service (ReDoS) vulnerability in the Soup Sieve library's selector compilation. The issue arises from exponential backtracking in the IDENTIFIER/CSS_ESCAPES regex when processing a sequence of ambiguous digit-escapes (\9) in CSS selectors. This vulnerability can cause significant delays or hangs during selector compilation, impacting availability. It affects versions from 1.1.0.2090 up to but not including 3.0.2_3. The flaw is fixed in version 3.0.2_3 and later. Exploitation requires an application to compile untrusted selector strings, which is uncommon but possible in certain user-driven query or scraping services.
SvelteKit is a framework for rapidly developing robust, performant web applications using Svelte. From version 2.60.1 until 3.1.1, applications using the experimental remote functions flag could assign the same generated identifier to separate non-exported query.batch functions. When those private functions shared a request batch, arguments intended for one function could be passed to another function, causing unexpected cross-function processing and possible disclosure of function arguments. This issue is fixed in 3.1.1.
The @opentelemetry/instrumentation-http package for Node.js versions >=0.204.0 and <0.222.0 improperly handles sensitive query parameters in incoming HTTP requests. While outgoing client spans redact sensitive URL query parameters, incoming server spans do not, resulting in raw query strings—including credentials like AWS presigned URLs, Azure SAS tokens, and GCS signed URLs—being recorded in plaintext in the url.query attribute. This sensitive information is then exported to the tracing backend, exposing valid credentials to anyone with access to telemetry data. The issue is patched in version 0.222.0, which redacts sensitive query parameters by default for incoming spans and introduces a redactedQueryParamsServer option for customization.
sqlite3 provides Ruby bindings for the SQLite3 embedded database. Prior to 2.10.2, sqlite3-ruby casts Ruby string lengths to int before passing SQL through Database#prepare, bound String or Blob values through Statement#bind_param, and String or Blob results from Ruby-defined SQL functions and aggregates through Database#create_function and Database#create_aggregate. On 64-bit platforms, a string of 4 GiB (2^32 bytes) or larger can wrap the length so SQLite processes only a prefix. A truncated SQL string can drop trailing clauses such as a WHERE condition, while a truncated bound value matters only when the application validated the full value before binding it. Exploitation requires the application and server to accept and retain the unusually large attacker-controlled string. If a dropped SQL clause contained a bind placeholder, binding raises SQLite3::RangeException instead of running the query. This issue is fixed in version 2.10.2.