The Product Filter for WooCommerce by WBW plugin for WordPress versions up to 3.4.6 has a missing authorization vulnerability in its 'filtersFrontend' AJAX action. This flaw allows unauthenticated attackers to manipulate query parameters and enumerate non-public WooCommerce products, including draft and pending items. Attackers can also force unbounded queries that return all products in a single request.
The Relevanssi – A Better Search WordPress plugin up to version 4.28.5 contains a stored cross-site scripting (XSS) vulnerability via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. Exploitation requires that both comment indexing and comment highlighting options are enabled, and the malicious payload activates when a visitor accesses a singular page through a Relevanssi search-result permalink with the highlight query parameter.
MariaDB Connector/J versions 3.0.0 through before 3.3.7, 3.4.0 through before 3.4.5, and 3.5.0 through before 3.5.11 have a vulnerability where the connector does not properly guard against changes to the character_set_results session variable. This allows a malicious or compromised server to switch the character set away from UTF-8 without the client noticing, causing incorrect decoding of query results. This can lead to integrity issues where application-side validation or escaping based on string values can be bypassed. The vulnerability requires control of the server side of the connection and does not impact confidentiality or availability. Fixed versions are 3.3.7, 3.4.5, and 3.5.11.
CVE-2026-63414 is an authorization vulnerability in the Shopify Rails engine 'shopify_app' affecting versions from 22.1.0 up to but not including 23.0.3. The flaw allows an attacker with a valid Shopify session token for one shop to supply a different shop identifier in a query parameter, causing the application to incorrectly treat the requested shop as the current one. This can lead to unauthorized access to data or actions scoped to another shop. The issue is fixed in version 23.0.3.
Element Call versions from 0.16.0 up to but not including 0.20.3 log the password URL query parameter in error report logs (rageshakes). These logs are shared with the application operator when users submit error reports, potentially exposing the shared password used to encrypt calls and compromising call confidentiality. The issue is fixed in version 0.20.3. Upgrading prevents future disclosures but does not remove passwords from previously collected logs, which require manual cleanup by the log-server operator.
WIT SynApps Runtime through 1.4.11 contains a pre-authentication reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject and execute arbitrary JavaScript by submitting a crafted LINK query parameter to the /System/Session-1 endpoint. Attackers can exploit this flaw to harvest credentials, manipulate the login flow, access browser-visible data, and perform same-origin requests to controller endpoints, including an origin-switch primitive against the internal controller in Cloud RIA scenarios.
The Majestic Support – The Leading-Edge Help Desk & Customer Support Plugin plugin for WordPress is vulnerable to generic SQL Injection via the 'columns (array keys)' parameter in all versions up to, and including, 1.2.2 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 subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Any authenticated WordPress user with Subscriber-level access can exploit this because the 'saveusereraserequest' task is whitelisted for front-end customer use, the plugin auto-provisions a help-desk record for every WordPress account, and the only guard is a nonce the attacker legitimately obtains from their own 'Add erase request' page.
CVE-2026-118959 is a vulnerability in Red Hat Build of Keycloak involving improper authentication. It arises from incorrect handling of the kc_action query parameter in authorization requests, which can cause mandatory user actions like profile verification or terms acceptance to be bypassed. This allows users with valid credentials to skip administrative requirements and gain access without completing necessary steps. The vulnerability is rated medium severity with a CVSS score of 5.4. No patch or mitigation meeting Red Hat's criteria is currently available.
A vulnerability in Keycloak Policy Enforcer allows any authenticated user to bypass all authorization policies, including role, scope, and UMA permission checks. This occurs when an attacker includes the configured access-denied page path within a request URL, either as a path segment or a query parameter, enabling unauthorized access to protected resources. The flaw affects Keycloak versions prior to 26.6.4 and 26.0.10. A fix is available in these versions.
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 does not verify that set-path-with-query values in wasmtime-wasi-http are paths, so absolute-form URLs are written verbatim as the HTTP/1.1 request target while the connection uses the allowed authority. A malicious guest can supply an absolute URL that a forward proxy or gateway at that authority honors, reaching hosts disallowed by embedder filtering policies.
The Waline login endpoint in @waline/vercel before version 1.41.0 accepts a non-string email value, which leads to a MongoDB query filter that matches all users. This causes the login process to verify the submitted password against the first-registered user (the administrator) without requiring the correct email. This vulnerability enables partial authentication bypass, user enumeration, and credential-stuffing amplification against the administrator account.
A vulnerability in i18next-http-backend prior to version 4.0.4 allows injection via unencoded language and namespace values in URL templates. This can let an attacker manipulate query parameters in translation requests, potentially exposing other namespaces or tenants or altering backend behavior. The issue is fixed in version 4.0.4.