Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to enforce the channel Access Control Policy's file download permission check when serving file metadata and thumbnails through the drafts, scheduled posts, and post edit history endpoints, which allows an authenticated user who has lost eligibility under the policy to view metadata and thumbnails of file attachments via those endpoints, even though direct file access is correctly denied. Mattermost Advisory ID: MMSA-2026-00740
Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to bound the resources consumed while processing an uploaded custom emoji image which allows an authenticated user with default permissions to make the server unresponsive for all users via repeated custom emoji uploads.. Mattermost Advisory ID: MMSA-2026-00720
Mattermost versions 11.7.x <= 11.7.11 fail to sanitize channel mentions when rendering permalinked posts, which allows an authenticated user to discover the display names of private channels they do not have access to via a permalink to a post that mentions the channel.. Mattermost Advisory ID: MMSA-2026-00721
A vulnerability in Linux Mint Update Manager's mint-refresh-cache component allows local users with sudo privileges to inject arbitrary command-line arguments into the privileged Synaptic process. This occurs because the --parent-window-id parameter is not validated as an integer, enabling command injection and arbitrary code execution as root. The issue affects multiple Linux Mint versions from 5.4.8 up to but not including fixed versions 5.5.4.3, 5.5.9.1, 5.8.8.1, 5.9.8.1, 6.0.9.1, and 6.1.5.1. The vulnerability is classified as CWE-88 Argument Injection and has a high severity CVSS 4.0 score of 8.5.
The WP Instant Feeds WordPress plugin up to version 1.3.4 is vulnerable to stored cross-site scripting (XSS) via the 'data[images][][url]' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts. The flaw is exploitable through a cache-write AJAX endpoint that relies solely on a nonce check tied to a user ID 0 nonce, which is publicly accessible on any front-end page rendering a feed. This enables attackers to harvest the nonce and perform the injection without authentication.
WarehousePG (WHPG) 6.27.1 through 6.27.7 and 7.2.1 through 7.6.1 are affected by an out-of-bounds write vulnerability (CWE-787) in gpfdist, the file server used to load and unload external tables. When gpfdist attaches a request to a session, it sizes two internal arrays from the client-supplied X-GP-SEGMENT-COUNT header and writes to them at the index given by the X-GP-SEGMENT-ID header, without checking that the index is non-negative and smaller than the count (CWE-129). gpfdist does not authenticate callers unless gpfdists is used with client certificate verification, so an attacker who can reach the gpfdist port can crash it with a single HTTP request, failing every external table load or unload that uses that gpfdist instance. gpfdist is normally reachable only from the cluster's internal network.
The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. The vulnerability exists because the Google Pay Express Checkout endpoint (`/?wc-api=google_pay_express`), handled by `startCheckoutDataWithNormalizedCustomerData`, accepts an attacker-controlled `paymentData.email` value and passes it to `createOrGetGuestCustomer()`, which resolves the submitted email to any existing WordPress user via `get_user_by('email', ...)` and then calls `wp_set_current_user()` and `wp_set_auth_cookie()` for the resolved user ID without verifying ownership of the email address, a password, a nonce, an authentication token, or any proof of payment from the payment provider. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover. The endpoint is entirely unprotected with no capability check, nonce validation, or payment-provider signature verification applied, and administrator email addresses are frequently discoverable via the WordPress REST API user enumeration endpoint (`/wp-json/wp/v2/users`), author archive pages, Gravatar lookups, or site contact footers.
The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. The vulnerability exists because the `new_customer_account()` function stores the raw return value of `wp_create_user()` — including a `WP_Error` object returned on username collision — into the order's `tp_userid` post meta before the `is_wp_error()` guard is evaluated; the `add_customer_details_to_thankyou_page()` callback subsequently reads that meta and casts it with `(int)`, causing PHP to coerce any object to integer `1`, after which `wp_set_current_user(1)` and `wp_set_auth_cookie(1)` are called unconditionally. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the `new_username` parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.
NocoDB versions prior to 2026.09.0 contain an authorization bypass vulnerability in the extract-ids.middleware.ts component. This flaw allows authenticated users with Viewer access on one base to use an MCP token ID in the query string to access metadata of another base, including table lists and member email addresses. The vulnerability does not allow modification or denial of service but exposes sensitive information across bases.
NocoDB versions before 2026.10.1 have an information disclosure vulnerability that allows unauthenticated attackers to download data exports by reconstructing predictable file paths. Attackers can derive these paths using table id, base, table and view titles, and export time, enabling access to full exports including fields hidden from public shared views.
Apache Iggy server versions through 0.9.0 have an insufficient session expiration vulnerability in their HTTP transport. The vulnerability arises because JSON Web Tokens (JWTs) identify users only by numeric user ID, and new users receive the lowest available ID. If an administrator deletes a user, the deleted user's unexpired or refreshed token can authenticate as a new user who receives the same ID, inheriting that user's permissions. This affects only deployments with HTTP enabled. Upgrading to version 0.10.0 resolves the issue.
Grav from 2.0.0 before 2.2.18 contains a Twig injection vulnerability that allows media-only accounts and anonymous uploaders to execute Twig by placing delimiters in image titles, alt text, class, id, or file names. Attackers can combine injected Twig with the autoescape tag to serve script to every page visitor, including super admins, or expose unpublished page content.
NocoDB before 2026.08.0 contains an authorization bypass vulnerability that allows anonymous share link holders to access records excluded by a shared view's row filter, because the read-by-primary-key path ignores the view's filters. Attackers can request the public attachment-download or nested-link listing routes with a record id to mint signed download URLs for hidden files and read linked-record data.
NocoDB before 2026.08.1 contains an authorization bypass vulnerability that allows authenticated Creators to access another tenant's external database by reusing a victim source id when adding a source. Because NcConnectionMgrv2 caches connections by bare source id, attackers can reflect the victim's cached database schema and read, update, and insert records through their own base models.
NocoDB before 2026.09.0 contains a missing authorization vulnerability in the job status polling endpoint of jobs.controller.ts that lacks an @Acl decorator. Unauthenticated attackers with a job id can read buffered status messages and completion payloads, exposing signed export download URLs or new base identifiers.
vLLM from 0.28.0 before 0.33.0 contains an improper input validation vulnerability that allows unauthenticated attackers to crash the shared EngineCore by sending out-of-range prompt token ids when served with --skip-tokenizer-init. Attackers can submit a large positive token id to /v1/completions, /v1/embeddings, or /pooling, bypassing the tokenizer-gated vocab check and causing a fatal embedding index error that denies service to all tenants.