| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| When the ClickHouse plugin uses Native protocol (the default) with PDC or secure SOCKS, it asks for TLS but the connection library ignores that and talks to ClickHouse in the clear. Username, password, queries, and results can be read on the hop after the proxy. The server certificate is never checked, and a configured client certificate is not sent. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| This CVE ID has been rejected. |
| GitLab has remediated a vulnerability in the GitLab AI Gateway component affecting all versions of the AI Gateway from 18.9.0 to 19.0.12, 19.1 to 19.1.7, and 19.2 to 19.2.2 that could have allowed an authenticated user with Duo Agent Platform access to redirect model requests to an externally-controlled endpoint via crafted model metadata, resulting in the disclosure of Google Vertex AI or AWS Bedrock cloud service credentials. |
| The CMP WordPress plugin before 4.1.18 does not enforce an option-name allow-list when importing settings via one of its AJAX actions, allowing users with the Editor role (when the administrator has granted the Editor role access to the CMP WordPress plugin before 4.1.18's admin-bar controls) to update arbitrary WordPress options, including options that lead to privilege escalation to Administrator. |
| The Mobile App for WooCommerce: ShopApper Mobile App Builder Service for WooCommerce WordPress plugin through 0.4.62 does not verify that the requesting user owns the customer profile being queried through one of its REST endpoints, allowing any authenticated user (e.g. a customer/subscriber) to retrieve other users' personal data, including their email address, name, and roles. |