A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1.
For an attack to be executable, the Airlock Gateway needs to have 'Smart Form Protection' (or the corresponding expert settings) enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references. The buffer overflow then happens during the parsing of that HTML response. Such a response can come either from a malicious or compromised backend, or from an otherwise trusted backend that returns attacker-supplied HTML, e.g. an application that stores and serves plain user-provided HTML files.
Successfully exploiting the vulnerability can enable an attacker to perform a DoS attack or, in the worst case, an RCE attack against the Airlock Gateway in front of the affected backend. Compromising the functionality of the Airlock Gateway could in this way also affect the availability and protection of other well-intentioned backends deployed behind the same Gateway.
The Meow Gallery plugin for WordPress is vulnerable to generic SQL Injection via the 'limit' parameter in all versions up to, and including, 5.5.9 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.
The BuddyPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 14.5.0. This is due to missing authorization checks in the `bp_nouveau_ajax_get_single_activity_content` AJAX handler. The function only verifies a nonce that is publicly exposed to any visitor who loads a BuddyPress page, but does not call `bp_activity_user_can_read()` to verify the user has permission to view the activity. This makes it possible for unauthenticated attackers to read private group activity content by iterating activity IDs.
An incorrect implementation of authentication algorithm vulnerability in the SSO API in Synology DiskStation Manager (DSM) before 7.2.2-72806-5 and 7.3.1-86003-1 (7.2.1-69057 is not affected) allows remote attackers to read or write arbitrary files and conduct denial-of-service attacks with prior knowledge of the distinguished name (DN).
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Rymera Web Co Product Feed PRO for WooCommerce woo-product-feed-pro allows Path Traversal.This issue affects Product Feed PRO for WooCommerce: from n/a through 13.5.8.
Deserialization of Untrusted Data vulnerability in Rymera Web Co Product Feed PRO for WooCommerce woo-product-feed-pro allows Object Injection.This issue affects Product Feed PRO for WooCommerce: from n/a through 13.5.8.
The Contact Form 7 WordPress plugin before 6.2.5 does not check that the post a form submission says it was sent from is publicly viewable before resolving post-related mail-tags, allowing unauthenticated users to obtain the title, URL, author name and author email of private, draft and trashed posts where such tags are used in an email or message returned to the submitter.
A stack-based buffer overflow vulnerability exists in the FTP URL path parsing of United Chargers Grizzl-E Smart 40A EV chargers. This flaw allows network-adjacent attackers to execute arbitrary code without authentication. The vulnerability has been assigned CVE-2026-131812 and a CVSS rating of 7.5 by the Zero Day Initiative.
A remote code execution vulnerability exists in United Chargers Grizzl-E Smart 40A EV chargers that allows network-adjacent attackers to execute arbitrary code without authentication. The vulnerability involves downloading code without an integrity check. It has been assigned CVE-2026-131810 and a CVSS rating of 7.5 by the Zero Day Initiative.
A vulnerability in Open Robotics ROS 2 sros2 load_policy allows remote attackers to disclose sensitive information via XML External Entity processing. Exploitation requires user interaction, such as visiting a malicious page or opening a malicious file. The vulnerability has a medium severity rating with a CVSS score of 5.5 assigned by the Zero Day Initiative.
A denial-of-service vulnerability exists in Open Robotics RViz's MapDisplay component, specifically in the OccupancyGridUpdate functionality. This flaw allows network-adjacent attackers to cause a denial-of-service condition without requiring authentication. The vulnerability has been assigned a medium severity rating by the Zero Day Initiative with a CVSS score of 6.5.
A denial-of-service vulnerability exists in Open Robotics RViz due to an out-of-bounds read in the IntensityPCTransformer PointField component. This flaw can be exploited by network-adjacent attackers without authentication to disrupt affected systems. The vulnerability has a medium severity rating with a CVSS score of 6.5 assigned by the Zero Day Initiative.
A denial-of-service vulnerability exists in Open Robotics RViz's AxisColorPCTransformer PointField component. Network-adjacent attackers can exploit this flaw without authentication to cause a denial-of-service condition. The vulnerability has a medium severity rating with a CVSS score of 6.5 assigned by the Zero Day Initiative.
A denial-of-service vulnerability exists in Open Robotics RViz due to an out-of-bounds read in the XYZPCTransformer PointField component. Network-adjacent attackers can exploit this issue without authentication to cause a denial-of-service condition. The vulnerability has a medium severity rating with a CVSS score assigned by ZDI of 6.5. No affected versions or patches are currently specified.
The AI Puffer - MCP Server for Claude & ChatGPT, with AI Chatbot plugin for WordPress is vulnerable to Stored Cross-Site Scripting via AI-generated comment replies in all versions up to, and including, 2.5.28 due to insufficient sanitization of the AI model's output in the insert_comment_reply_logic() function, which saves replies with wp_insert_comment() and bypasses the kses filtering WordPress normally applies to comment content. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page, by submitting a comment that leads the AI model to reproduce an HTML payload in its automated reply. This is only exploitable when an administrator has configured a Comment Auto-Reply automation task with 'Action on reply' set to 'Approve' (the default is 'Hold for moderation'), and the attacker's comment has been approved.