IBM Langflow OSS versions 1.0.0 through 1.10.3 contain a vulnerability that allows authenticated users to exploit a built-in component to read arbitrary server environment variables. This exposure can leak sensitive secrets despite security controls intended to disable such custom components. The vulnerability is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) and has a CVSS 3.1 base score of 6.5, indicating medium severity.
CVE-2026-60023 is a high-severity vulnerability in Apache Answer versions prior to 2.0.2. It allows unauthorized users to retrieve deleted or pending answers through the single-answer read path if the parent question remains visible, exposing sensitive information that should not be accessible. The issue is fixed in version 2.0.2.
Statamic CMS's user-augmentation resolver, AugmentedUser::get in src/Auth/AugmentedUser.php, contains an explicit case for the handle that returns the user's raw two-factor recovery codes with no access restriction.
Eclipse Theia versions up to and including 1.73.1 contain a directory traversal vulnerability in the @theia/filesystem backend HTTP file-download endpoints. These endpoints convert client-supplied URIs directly to filesystem paths without restricting access to the workspace or allowed roots. In browser deployments, token enforcement is ineffective on HTTP requests, allowing unauthenticated clients to read any file accessible by the backend process, including sensitive files outside the workspace. Electron mode is not affected by this vulnerability via this path.
CVE-2026-17515 is a medium severity information exposure vulnerability in the MLSImport: IDX Plugin & MLS Plugin for Real Estate Listings WordPress plugin before version 7.0.4. The flaw arises because one of the plugin's AJAX actions lacks authorization and CSRF protections, allowing any authenticated user, including low-privileged subscribers, to read the import log file and import-related metadata of arbitrary posts. This could lead to unauthorized disclosure of potentially sensitive information stored in these logs and metadata.
CVE-2026-16993 is an information exposure vulnerability in the DHL Shipping Germany for WooCommerce WordPress plugin versions before 4.0.1. The plugin stores shipping labels containing customer names and postal addresses in a directory protected only by an Apache .htaccess file. On web servers that do not honor .htaccess files, such as nginx, unauthenticated attackers can download these shipping labels by requesting predictable filenames. This vulnerability leads to unauthorized disclosure of customer shipping information.
GeoDirectory WordPress plugin versions prior to 2.8.168 contain an information exposure vulnerability that allows any authenticated user with Contributor-level access or higher to retrieve email addresses of all registered users, including administrators. This occurs because the user-search handler does not restrict access properly. The vulnerability is identified as CVE-2026-16968 and is classified under CWE-200. It has a medium severity with a CVSS score of 6.5.
Passster WordPress plugin versions before 4.3.6 expose password-protected content in the public page response before password verification, allowing unauthenticated users to access protected content. This vulnerability leads to information disclosure without requiring authentication.
Passster WordPress plugin versions before 4.3.6 have a vulnerability that allows unauthenticated users to bypass category-based content protection on the WordPress REST API. This flaw exposes the full content, title, and excerpt of posts locked by category through the core REST API without authentication.
CVE-2026-16602 is a high-severity information exposure vulnerability in the Passster WordPress plugin before version 4.3.6. The plugin fails to verify post status before returning post content via an unauthenticated REST endpoint. This allows unauthenticated users to access content of non-public posts (draft, private, pending) on sites with a configured captcha provider.
Ghost, a Node.js content management system, had a vulnerability prior to version 6.54.1 where staff-level users could access hashed passwords of other staff users via the Ghost Admin API. This exposure could allow offline password-guessing attacks potentially leading to account takeover, although device verification was intended to mitigate unauthorized logins. The vulnerability is fixed in version 6.54.1.
Flowise versions prior to 3.1.3 contain a vulnerability where the POST /api/v1/oauth2-credential/refresh/:credentialId endpoint is accessible without authentication. This endpoint decrypts stored OAuth credentials and returns refreshed access tokens, exposing sensitive information to unauthorized actors. An attacker with knowledge of a credential ID can obtain access tokens to connected services and potentially exhaust refresh-token quotas. The issue is fixed in version 3.1.3.
Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. Prior to 3.1.3, Flowise GET /api/v1/upsert-history returns the entire server-wide upsert history instead of being scoped to the requesting user, tenant, or workspace. The response can exceed 100MB and includes sensitive configuration data, including Vector Store settings such as Qdrant Server URL and collection name. The observed behavior indicates missing or insufficient authorization checks, workspace/project/tenant isolation, and pagination or limits, exposing integration parameters and infrastructure details that may enable further targeted attacks. This issue is fixed in version 3.1.3.
CVE-2026-15236 is a high-severity information exposure vulnerability in the Gallery for Google Photos WordPress plugin before version 1.2.1. The plugin fails to properly restrict access to stored third-party OAuth credentials, exposing persistent access and refresh tokens to unauthenticated users. This exposure can lead to long-term compromise of the linked Google Photos account.
The PixelYourSite – Your smart PIXEL (TAG) & API Manager plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 11.2.1 via the getWooPurchaseEventParams. This makes it possible for unauthenticated attackers to extract WooCommerce purchase metadata — including product names, product IDs, quantities, per-item prices, order totals, currency, and order/transaction IDs — for any existing order by supplying an invalid or arbitrary order key. This is exploitable against any known or enumerated order ID, as the plugin resolves the order from the URL path variable alone and emits the full woo_purchase tracking payload into the page HTML via the pysOptions JavaScript object across its Facebook, Google Analytics, and Google Tag Manager integrations regardless of key validity.
The Jeg Kit for Elementor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.1 via the `enqueue_scripts()` method in `class/dashboard/class-dashboard.php`. The plugin injects a `JkitDashboardOption` JavaScript object containing full plugin inventory (names, versions, paths, active status), system environment details (WordPress version, PHP version, site URLs, server capabilities), and potentially third-party API credentials (Mailchimp API key via `jkit_user_data`) as an inline script on the `post.php` admin page. Because this data is output without any capability check beyond post editing access, any authenticated user with Contributor-level access or above can view this sensitive configuration data by inspecting the page source. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive site configuration data, installed plugin details, and potentially third-party API keys.
The Mapster WP Maps WordPress plugin before 1.24.0 does not perform any authorization or post-status check on a public REST endpoint, allowing unauthenticated users to retrieve the title and full content of any post regardless of its status, including unpublished (draft, pending, private, and trashed) posts.
gemini-bridge is a lightweight MCP server bridging AI agents to Google's Gemini AI via the official CLI. From 1.0.0 until 1.3.1, consult_gemini_with_files in inline mode read any file path supplied in the files argument without confining it to the working directory, then forwarded the contents to the Gemini CLI. Because the caller also controls query, the file contents are echoed back through the Gemini round-trip (and sent to Google), making this an arbitrary local file read. This issue is fixed in version 1.3.1.
Wings is the server control plane for Pterodactyl, a free, open-source game server management panel. Prior to 1.12.3, {{config.}} placeholders in egg configuration-file templates allow a low-privileged user to read {{config.token}}, {{config.token_id}}, and {{config.docker.registries}} from the full daemon configuration. This issue is fixed in version 1.12.3.