Vulnerabilities

Formwork before 2.3.11 contains a stored cross-site scripting vulnerability in visit tracking that records the Referer header host unescaped. Unauthenticated attackers can craft malicious Referer headers to inject markup that executes in administrator browsers when viewing the Statistics panel.

rust-iot-platform through commit 5df942ab contains an authentication bypass vulnerability where most REST API routes lack authentication guards in their handler signatures. Unauthenticated attackers can create, update, list, retrieve, and delete user accounts by directly accessing unprotected endpoints without providing valid credentials.

rust-iot-platform through commit 5df942ab stores user passwords in cleartext without hashing in the user model. Attackers can read API responses from user retrieval and listing routes to obtain plaintext credentials for all accounts.

argocd-mcp 0.8.0 binds its HTTP transport to every network interface and accepts MCP sessions without requiring caller credentials when ARGOCD_API_TOKEN is configured. Attackers who can reach the listener can invoke the full tool surface using the operator's stored token to create applications, request syncs, and modify Argo CD resources.

su-exec through 0.3 fails to validate numeric user and group identifiers parsed with strtol before assigning to uid_t and gid_t, allowing truncation of out-of-range values to zero. Attackers can supply large numeric identifiers that truncate to root's identifier, causing su-exec to execute target programs with root privileges instead of intended unprivileged accounts.

BookStack before 26.05.4 contains a remote code execution vulnerability in the portable ZIP import functionality that allows users with Import Content and Create Books permissions to upload a PHP polyglot file as a book cover. Attackers can bypass image extension validation by embedding a PHP file with a .php filename in the ZIP archive, which is stored in the public web root and executed by unauthenticated requests.

Cockpit CMS before 2.14.1 contains an account enumeration vulnerability in the auth check endpoint due to timing discrepancies in password verification. Attackers can measure response times across multiple requests to determine which accounts exist by observing that existing accounts trigger bcrypt verification while non-existent accounts return immediately.

Shinobi before commit 5a76c74f contains a hardcoded connection key in the child node service that allows unauthenticated attackers to execute arbitrary database queries. Attackers reaching the child node port can present the hardcoded key during WebSocket handshake, then dispatch SQL queries through the onWebSocketDataFromChildNode handler to read and modify user records and camera configuration.

Skyvern before 1.0.45 contains a sandbox escape vulnerability in TextPromptBlock that renders prompts twice, first through a sandboxed Jinja environment and then through an unsandboxed environment. Attackers can inject malicious Jinja template syntax through workflow parameters or upstream block output to execute arbitrary code with server process privileges.

The Sigma Forms Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.4.5 via the handle_form_submission function. This is due to the plugin dynamically granting the unfiltered_upload capability to all users during form submissions and bypassing MIME type validation when allowed_file_types is not configured. This makes it possible for unauthenticated attackers to execute code on the server. Several default pre-built templates including Job Application, Support Ticket, and Wholesale Application have file upload fields with no file type restrictions configured by design, making this vulnerability immediately exploitable upon installation.

A security vulnerability has been detected in macrozheng mall up to 1.0.3. This impacts an unknown function of the file /order/submit of the component Order Submission. The manipulation leads to race condition. It is possible to initiate the attack remotely. The attack is considered to have high complexity. The exploitability is said to be difficult. The vendor deleted the GitHub issue for this vulnerability without and explanation.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: gro: properly validate BIG TCP aggregation criteria<br /> <br /> When GRO attempts to aggregate packets beyond GRO_LEGACY_MAX_SIZE (64KB),<br /> BIG TCP should only be permitted for plain IPv4 TCP and plain IPv6 TCP<br /> (with sufficient MAC header room to insert the temporary HBH jumbo header).<br /> <br /> However, commit b1a78b9b9886 ("net: add support for ipv4 big tcp")<br /> loosened the check in skb_gro_receive(), leading to several issues:<br /> <br /> 1. skb_gro_receive() checked skb_headroom(p) instead of the actual space<br /> before the MAC header (p-&gt;mac_header). Because skb_headroom(p) includes<br /> mac_len, crafted frames (e.g. injected via AF_PACKET) can pass the check<br /> with p-&gt;mac_header head,<br /> causing an out-of-bounds write and wrapping skb-&gt;mac_header.<br /> 2. It allowed non-IP protocols such as software VLAN (ETH_P_8021Q /<br /> ETH_P_8021AD) to aggregate beyond 64KB because<br /> p-&gt;protocol != ETH_P_IPV6 was true.<br /> 3. It checked p-&gt;encapsulation instead of NAPI_GRO_CB(skb)-&gt;encap_mark,<br /> allowing encapsulated flows (e.g. SIT / IPv6-in-IPv4) to aggregate<br /> beyond 64KB.<br /> <br /> Fix skb_gro_receive() to strictly enforce:<br /> - NAPI_GRO_CB(skb)-&gt;proto == IPPROTO_TCP<br /> - Not encapsulated (!NAPI_GRO_CB(skb)-&gt;encap_mark &amp;&amp; !p-&gt;encapsulation)<br /> - Protocol must be either ETH_P_IP or ETH_P_IPV6<br /> - If ETH_P_IPV6, p-&gt;mac_header must be at least<br /> sizeof(struct hop_jumbo_hdr)<br /> <br /> Returning -E2BIG from skb_gro_receive() ensures that packets which cannot<br /> become BIG TCP are cleanly flushed at