The BuddyPress plugin for WordPress up to and including version 14.5.0 has a vulnerability that allows unauthenticated attackers to access private group activity content. This occurs because the AJAX handler bp_nouveau_ajax_get_single_activity_content only verifies a nonce that is publicly accessible, but does not check if the user has permission to view the activity. This missing authorization check leads to sensitive information exposure.
A vulnerability in Airlock Gateway versions 8.5.2 and earlier, and 8.6.0, allows attacker-controlled HTML in backend responses to exploit the Smart Form Protection feature. This can lead to a buffer overflow during HTML parsing, potentially causing Denial of Service (DoS) or Remote Code Execution (RCE). The issue is fixed in versions 8.5.3 and 8.6.1.
The Meow Gallery plugin for WordPress contains a SQL Injection vulnerability in the 'limit' parameter affecting all versions up to 5.5.9. This flaw allows authenticated users with administrator-level privileges or higher to inject additional SQL queries, potentially exposing sensitive database information. The vulnerability arises from insufficient escaping and lack of proper query preparation.
Dell PowerStore 500T contains an integer underflow vulnerability (CWE-191) that could be exploited by an attacker to cause denial of service of a cryptographic service. This vulnerability affects version 0 and is fixed in version 5.1.0.0-2798105 or later. The vulnerability has a high severity with a CVSS score of 8.1.
CVE-2026-132125 is a privilege escalation vulnerability in Weblate versions 5.0 through 2026.11.2. When a user with componentlist.edit permission deletes a component list, stale Group.projects database entries remain. This causes 'From component list' team members to inherit full project roles, including project.edit, potentially across private projects.
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.
This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.
Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
Craft CMS from 5.0.0 before 5.11.4 contains an improper session management vulnerability that fails to invalidate existing sessions when 2FA is enabled and allows disabling 2FA without re-authentication. Attackers holding a hijacked or stale session can retain full account access and silently remove 2FA without the password, authenticator code, or recovery code.
Craft CMS from 5.0.0 before 5.11.4 contains a stored cross-site scripting vulnerability that allows low-privilege control panel users to inject JavaScript by poisoning cached license data. Attackers can store a malicious licensed domain via the app/process-api-response-headers endpoint, which executes unescaped in administrators' dashboard license-mismatch warnings.
Craft CMS versions from 5.0.0 up to but not including 5.11.4 contain a critical remote code execution vulnerability in the ImageTransforms::normalizeTransform() function. This flaw allows attackers to instantiate arbitrary PHP classes by supplying a crafted class:null parameter with a __class key. Exploitation can occur via Craft Commerce's payments/pay redirect template when calling customer.photo.getUrl() with a malicious transform, enabling execution of classes such as yii\rbac\PhpManager and arbitrary PHP code execution. The vulnerability is fixed in version 5.11.4.
Craft CMS from 5.0.0 before 5.11.4 contains an incomplete blocklist fix that allows attackers who can author entry type title formats to write arbitrary files using ZipArchive or XMLWriter classes. Attackers can abuse the non-sandboxed renderObjectTemplate() renderer to write attacker-controlled content into the web docroot, achieving remote code execution.
Craft CMS from 5.0.0 before 5.11.5 contains an sql injection vulnerability that allows authenticated low-privilege users to inject raw SQL by passing nested array parameters into Element::findOne() criteria. Attackers can set the query's where property through endpoints like users/delete-address and users/save-address to perform blind boolean or time-based injection and read database contents.
Craft CMS from 5.0.0 before 5.11.5 contains a missing authorization vulnerability in ChartsController::actionGetNewUsersData() that lacks a viewUsers permission check. Authenticated control panel users can POST to the charts/get-new-users-data action to read aggregate user-registration time series and totals for the site or any user group.
WWBN AVideo from 6.5 contains a stored cross-site scripting vulnerability that allows users with upload permission to inject script by submitting a javascript: scheme videoLink for embed videos. The unvalidated URL is rendered into an iframe src in videoEmbeded.php and PlayerSkins.php, executing for viewers including administrators and enabling creation of new administrator accounts.
The AppPresser – Mobile App Framework plugin for WordPress is vulnerable to generic SQL Injection via the 'appp_cam_file[name]' parameter in all versions up to, and including, 5.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Although the AJAX handler is registered for unauthenticated users, the only authorization gate is a nonce check, and the required nonce is only emitted to logged-in users viewing a page containing the [app-camera] shortcode, making Subscriber-level access the effective minimum requirement for exploitation.
The WP Coder – Insert & Manage Code Snippets plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'alt_text (WP media REST) → _wp_attachment_image_alt post meta' parameter in all versions up to, and including, 5.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires that an admin-authored image-type snippet exists on the site, as the attacker uploads an image via the standard WordPress media REST endpoint, sets its Alt Text to a double-quote-based payload that survives WordPress core's sanitize_text_field(), and then publishes a post embedding the shortcode.
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 5.3.3. The vulnerability exists because the `matches_mcp_endpoint()` function applies an unanchored regular expression (`#/(?:woocommerce|dokan)/mcp(?:/|$)#`) against the entire `REQUEST_URI` including the query string, meaning any request that contains the literal substring `/dokan/mcp/` or `/woocommerce/mcp/` anywhere in its URI — including inside a query parameter value — is incorrectly treated as a trusted internal MCP context, causing `scope_product_permissions()` to unconditionally return `true` on WooCommerce's `woocommerce_rest_check_permissions` filter regardless of whether the caller is authenticated. This makes it possible for unauthenticated attackers to read full authenticated WooCommerce REST product records for any published product — including private underscore-prefixed meta, purchase notes, downloadable file URLs for paid digital products, catalog-hidden products, and edit-context representations — across the `/wc/v1`, `/wc/v2`, `/wc/v3`, and `/wc-analytics` REST namespaces. The bypass is triggered by appending a query parameter whose value contains the literal string `/dokan/mcp/` to any WooCommerce REST product endpoint (e.g., `/wp-json/wc/v3/products/{id}?x=/dokan/mcp/`); note that percent-encoding the slashes prevents the bypass, as the unencoded literal slash characters are required for the regex to match.
The Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.0.10 This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to create, modify, and delete entries in the site-wide global button-preset store, and inject arbitrary CSS rules into the generated plus-button-presets stylesheet served to all site visitors.
The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.7.7 via the 'key' parameter. This makes it possible for unauthenticated attackers to extract full invoice and receipt records including customer full name, email address, phone number, invoice line items and totals, and the invoice's real access key. This is exploitable via the unauthenticated public routes invoices__view_by_key and transactions__view_receipt_by_key, which apply no ownership, capability, or nonce check before passing the attacker-supplied key into the ORM lookup.
The WP Maps – Google Maps, OpenStreetMap, Mapbox, Store Locator with Search, Filters & Listings plugin for WordPress is vulnerable to generic SQL Injection via the 'csv_columns' parameter in all versions up to, and including, 5.0.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 administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.
In Eclipse versions 1.5-1.6.13, 2.0.0-2.0.22 and 2.1.0-2.1.2, the client library libmosquitto does not reject Will messages with payloads greater than 65535 bytes when calling `mosquitto_will_set()` or `mosquitto_will_set_v5()`. This results in up to 65535 bytes of uninitialised heap memory being transmitted as the Will.
This can be mitigated by only passing payloads with a maximum length of 65535 bytes.