Vulnerabilities

Supabase Capgo before 12.128.2 contains an authorization bypass vulnerability in the SECURITY DEFINER record_build_time RPC function that allows unauthenticated attackers to insert arbitrary build-time records. Attackers can exploit this by calling POST /rest/v1/rpc/record_build_time with a public API key to poison billing and quota data for any organization, enabling resource exhaustion and cross-tenant billing manipulation.

Capgo before 12.128.2 enforces mandatory two-factor authentication only at the UI level. Sensitive Organization (ORG) management API endpoints (e.g., editing organization details, inviting users) do not validate 2FA completion on the backend. An authenticated Admin user who has not enabled 2FA can replay or modify a previously captured ORG API request to perform privileged organization actions, bypassing the globally enforced 2FA requirement.

Capgo before 12.128.2 contains a broken object level authorization (BOLA) vulnerability in the POST /build/start/:jobId and POST /build/cancel/:jobId endpoints. The handlers authorize the request based only on the attacker-controlled app_id supplied in the request body and never verify that the jobId in the URL belongs to that app_id (or the same tenant/org) before issuing privileged builder commands with the server-held builder API key. An authenticated user with the app.build_native permission for any app they control can start or cancel arbitrary builder jobs belonging to other tenants by supplying a victim jobId, resulting in cross-tenant build sabotage (denial of service), unauthorized compute actions, and potential billing impact.

Capgo before 12.128.2 contains a cross-domain SSO account takeover vulnerability in the provision-user endpoint that allows attackers to merge arbitrary victim accounts based on email match without validating SSO provider domain authorization. An attacker with enterprise org admin access and a malicious IdP can forge SAML assertions containing victim email addresses to trigger account merge and gain full access to victim accounts, organizations, and data.

Capgo before 12.128.2 fails to enforce limited_to_orgs and limited_to_apps constraints on subkeys provided via x-limited-key-id header in middlewareKey function. Attackers can bypass subkey scope restrictions by referencing their own subkeys, causing all downstream route handlers to use the unrestricted parent key instead of the scoped subkey.

Capgo before 12.128.2 contains a broken authentication vulnerability in its API key generation mechanism. API keys are exposed in frontend requests, and the backend fails to validate that keys are securely generated and bound to the authenticated user. An attacker can tamper with the API key parameter in the generation request and supply arbitrary values, generating custom API keys without proper authorization, which can lead to unauthorized access to protected endpoints.

Capgo before 12.128.2 allows non-admin API keys to read webhook signing secrets via Supabase REST due to insufficient row-level security policies on the webhooks table. Attackers can retrieve the webhook secret and forge valid X-Capgo-Signature headers to send authenticated webhook events to configured receivers, breaking webhook authenticity and integrity.

The AdRotate Banner Manager plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 5.17.7 via the 'banner' attribute of the adrotate shortcode. This is due to insufficient input validation and sanitization of the banner shortcode attribute before concatenation into a PHP code string wrapped in W3 Total Cache mfunc or Borlabs Cache fragment markers. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server. This vulnerability requires W3 Total Cache or Borlabs Cache support to be enabled in AdRotate settings.

Flowise through 2.2.7 contains a SQL injection vulnerability in the importChatflows API. Due to insufficient validation of the chatflow.id value, an authenticated user can supply a crafted JSON import file whose id field is concatenated unsanitized into a SQL IN clause, allowing arbitrary SQL to be executed, including blind and error-based extraction of data from the credential table.

picklescan before 0.0.29 fails to detect malicious pickle files that exploit idlelib.debugobj.ObjectTreeItem.SetText function in reduce methods. Attackers can craft pickle files with embedded code that bypasses picklescan detection and executes arbitrary commands when pickle.load() is called.

picklescan before 0.0.29 fails to detect malicious idlelib.calltip.Calltip.fetch_tip calls in pickle files, allowing remote code execution. Attackers can embed undetected payloads in pickle files that execute arbitrary code when loaded via pickle.load().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: skbuff: fix missing zerocopy reference in pskb_carve helpers<br /> <br /> pskb_carve_inside_header() and pskb_carve_inside_nonlinear() both copy<br /> the old skb_shared_info header into a new buffer via memcpy(), which<br /> includes the destructor_arg pointer (uarg) for MSG_ZEROCOPY skbs.<br /> Neither function calls net_zcopy_get() for the new shinfo, creating an<br /> unaccounted holder: every skb_shared_info with destructor_arg set will<br /> call skb_zcopy_clear() once when freed, but the corresponding<br /> net_zcopy_get() was never called for the new copy. Repeated calls<br /> drive uarg-&gt;refcnt to zero prematurely, freeing ubuf_info_msgzc while<br /> TX skbs still hold live destructor_arg pointers.<br /> <br /> KASAN reports use-after-free on a freed ubuf_info_msgzc:<br /> <br /> BUG: KASAN: slab-use-after-free in skb_release_data+0x77b/0x810<br /> Read of size 8 at addr ffff88801574d3e8 by task poc/220<br /> <br /> Call Trace:<br /> skb_release_data+0x77b/0x810<br /> kfree_skb_list_reason+0x13e/0x610<br /> skb_release_data+0x4cd/0x810<br /> sk_skb_reason_drop+0xf3/0x340<br /> skb_queue_purge_reason+0x282/0x440<br /> rds_tcp_inc_free+0x1e/0x30<br /> rds_recvmsg+0x354/0x1780<br /> __sys_recvmsg+0xdf/0x180<br /> <br /> Allocated by task 219:<br /> msg_zerocopy_realloc+0x157/0x7b0<br /> tcp_sendmsg_locked+0x2892/0x3ba0<br /> <br /> Freed by task 219:<br /> ip_recv_error+0x74a/0xb10<br /> tcp_recvmsg+0x475/0x530<br /> <br /> The skb consuming the late access still referenced the same uarg via<br /> shinfo-&gt;destructor_arg copied by pskb_carve_inside_nonlinear() without<br /> a refcount bump. This has been verified to be reliably exploitable: a<br /> working proof-of-concept achieves full root privilege escalation from<br /> an unprivileged local user on a default kernel configuration.<br /> <br /> The fix follows the pattern of pskb_expand_head() which has the same<br /> memcpy/cloned structure. For pskb_carve_inside_header(), net_zcopy_get()<br /> is placed after skb_orphan_frags() succeeds, so the orphan error path<br /> needs no cleanup. For pskb_carve_inside_nonlinear(), net_zcopy_get() is<br /> placed after all failure points and just before skb_release_data(), so<br /> no error path needs cleanup at all -- matching pskb_expand_head() more<br /> closely and avoiding the need for a balancing net_zcopy_put().