CWE-200: Information Exposure vulnerabilities

baserCMS versions 5.0.0 before 5.3.2 and 5.4.0 before 5.4.2 contain a path traversal vulnerability in the optional BcThemeFile plugin. An authenticated user with theme-file view permission can read certain files outside the theme directory by exploiting improper path validation. This can disclose sensitive application source code and configuration files, including database credentials and security salts. The plugin is disabled by default, and unauthenticated access is not sufficient. The issue is fixed in versions 5.3.2 and 5.4.2.

A vulnerability in the GTM Server Side plugin by stape.io for WordPress versions 2.0.0 up to but not including 2.1.48 allows unauthenticated attackers to cause the plugin to render another customer's full WooCommerce order data, including personally identifiable information (PII), into the page's JavaScript dataLayer. This exposure of sensitive information has been addressed in version 2.1.48.

A high-severity out-of-bounds read vulnerability exists in the odhcpd DHCPv6 IA parser used by OpenWrt. Versions from 17.01.0 up to but not including 25.12.3 improperly handle IA_NA or IA_PD options with bodies shorter than expected, leading to reading adjacent stack memory. This can disclose sensitive stack data such as stack canaries and ASLR-related information. The issue is fixed in version 25.12.3.

PraisonAI is a multi-agent teams system. From version 4.5.115 to before version 4.6.61, the published A2U advisory GHSA-f292-66h9-fpmf says unauthenticated A2U event streaming was fixed in praisonai 4.5.115. Current head still exposes the same A2U subscription and event routes without authentication when the operator starts the documented CLI entrypoint. The current CLI wrapper does not expose --api-key, does not install the common API-key middleware, and does not generate a token for A2U. It calls create_a2u_routes(app) directly. That helper only enforces auth if A2U_AUTH_TOKEN is already present; if the variable is missing, _authenticate_request() returns None and treats auth as disabled. This issue has been patched in version 4.6.61.

PraisonAI versions from 4.2.1 up to but not including 4.6.59 have an unauthenticated AgentOS FastAPI deployment surface. This allows unauthorized actors to invoke agent chat functionality without authentication, potentially exposing sensitive information and enabling unauthorized actions. The vulnerability has been fixed in version 4.6.59.

PraisonAI versions from 3.8.1 up to but not including 4.6.59 contain a path traversal vulnerability in the Dynamic Context Discovery feature. This flaw allows unauthorized reading of arbitrary files on the host filesystem by manipulating artifact tool arguments. The vulnerability has been fixed in version 4.6.59.

CVE-2026-56833 is a path traversal vulnerability in MervinPraison's PraisonAI affecting versions from 3.8.1 up to but not including 4.6.59. The Dynamic Context module improperly handles run_id and agent_id inputs, allowing an attacker with lower trust to read .jsonl and .log files outside the intended directory. This issue is fixed in version 4.6.59.

Otter Blocks WordPress plugin versions before 3.2.8 have a vulnerability where block visibility restrictions are bypassed when content is accessed via the WordPress REST API. This allows unauthenticated users to view block content intended to be restricted to certain user roles, logged-in users, post authors, categories, tags, or Stripe purchasers on the Pro tier.

CVE-2026-109934 is a vulnerability in the Otter Blocks WordPress plugin versions 3.1.1 up to but not including 3.2.8. The plugin incorrectly treats any post with the published status as publicly readable in its REST API, allowing unauthenticated users to access sensitive information such as manual excerpts of password-protected posts, content and titles of non-public post types, and WooCommerce coupon codes and descriptions. This exposure can lead to unauthorized disclosure of sensitive data.

draw.io Desktop is the official Electron build of draw.io. Prior to 31.4.4, draw.io Desktop is vulnerable to arbitrary local-file disclosure through the Electron main process's read-side IPC handlers. The readFile, getFileDrafts, getBkpFile, fileStat, isFileWritable, checkFileExists, and watchFile actions operate on a renderer-chosen filesystem path with no blessed-path (assertWritablePath) authorization. The only gates are validateSender — a URL-prefix origin check — plus, for readFile alone, a content "sniff" and a lexical appBaseDir prefix block. The write-side handlers (saveFile, writeFile, saveDraft, deleteFile) are all protected by assertWritablePath; the read side is not. The result is a read/write authorization asymmetry: any frame executing in the app's file:// origin can read the contents of local files that the same origin is explicitly forbidden to write. This issue is fixed in version 31.4.4.

The Click n Chat (Chat Widget Integration) WordPress plugin before 1.1.3 does not perform any authorization check on a lead-export handler, allowing unauthenticated users to download every captured contact record (names, email addresses and phone numbers).

The WholesaleX WordPress plugin before 3.0.9 does not protect or remove the user-import file it keeps in a publicly accessible location under a predictable name, allowing unauthenticated users to download the most recently imported user data, including any account passwords and customer contact and address details it contains.

The SureCart WordPress plugin before 4.9.5 does not restrict which related objects an anonymous visitor may include when reading a single upsell funnel through its REST API, nor strip private fields from those objects, allowing unauthenticated users to read merchant-private catalog data such as pricing, commission, stock, SKU and tax internals, including unpublished products.

The Booking Package WordPress plugin before 1.7.31 does not perform authorization checks before returning calendar-account configuration in a response, allowing unauthenticated users to disclose sensitive settings including the administrator's notification email addresses.

CVE-2026-94265 is a critical vulnerability in curl where HTTP redirects containing userinfo can cause curl to improperly retain and resend the original host's HTTP Negotiate authentication state. This allows a malicious server to force curl to send a Kerberos ticket to an untrusted third-party host, bypassing normal domain-scoping restrictions.

A vulnerability in libcurl's TFTP implementation allows a malicious TFTP server to cause the client to transmit sensitive data from previous unrelated operations. This occurs because the TFTP state machine does not properly validate state transitions against the requested transfer direction, enabling exposure of data from the handle's persistent read data pointer.

A vulnerability in the follow-redirects Node.js library versions 1.16.0 up to but not including 1.16.1 allows sensitive credential headers such as Authorization, Proxy-Authorization, and Cookie to be exposed to unauthorized remote servers. This occurs because the header removal logic fails when headers are provided as an array, causing these sensitive headers to be forwarded during cross-origin redirects without warning. The issue is fixed in version 1.16.1.

ApostropheCMS versions prior to 4.33.0 have a vulnerability where an unauthenticated user can access the GET /api/v1/<piece-type>/:_id/locales REST route without proper authorization checks. This allows the user to determine if a document exists and which locales it is published in, exposing sensitive metadata that should be restricted. The issue is fixed in version 4.33.0.

ApostropheCMS versions from 1.25.0 up to but not including 1.28.0, when configured with the Azure backend and SAS tokens enabled, leak account-level SAS tokens in public attachment URLs. This exposure occurs because the BlobServiceClient is constructed from a URL embedding the full SAS query string, which is then inherited by Azure SDK clients. The issue is fixed in version 1.28.0 and later.