CVE Vulnerability Catalog

The RT Mega Menu WordPress plugin before version 1.5.2 does not perform a capability check on the AJAX action that saves mega-menu configuration and per-menu-item settings. Its only gate is a nonce that any logged-in user can read from a standard admin page. A subscriber-level user can enable the mega menu on a site menu and store a menu-item style value that is rendered, without output escaping, into a style attribute on the public navigation. By breaking out of that attribute, the user persists a JavaScript event handler that executes for every visitor who hovers the navigation, including administrators, leading to session/site takeover.

The Meta Box WordPress plugin before version 5.13.1 does not verify that a user is authorized to delete the supplied attachment. This allows users with low privileges, such as Contributor, to permanently delete arbitrary media attachments belonging to other users.

The FluentBoards WordPress plugin before version 1.95.3 does not verify that the items selected for a board import operation belong to a board the requesting user is authorized to access. This allows any authenticated user with member access to a single board to copy and read the stages and tasks (including titles, descriptions and file attachments) of any other board on the site.

The JetEngine WordPress plugin before version 3.8.12 does not escape a post meta value before outputting it through one of its shortcodes. This allows users with the Contributor role and above to perform Stored Cross-Site Scripting attacks that execute in the context of higher-privileged users such as administrators.

The King Addons for Elementor WordPress plugin before version 51.1.76 does not escape a user-supplied grid setting before reflecting it into an HTML attribute in an unauthenticated AJAX response. This allows attackers to execute arbitrary JavaScript in the browser of a visitor who is tricked into loading a crafted page.

The Element Pack Addons for Elementor WordPress plugin before version 8.7.13 does not sanitize option values passed through certain data attributes before a bundled front-end library re-parses and renders them in the browser. This allows users with contributor-level access or higher to inject arbitrary JavaScript that executes in the session of any visitor who views the affected content.

The webtoffee-cookie-consent WordPress plugin before version 3.5.3 lacks authorization checks on several REST API routes. This allows unauthenticated attackers to export and delete stored visitor consent records, create posts, and modify the plugin's licensing state.

The Clever Mega Menu for Visual Composer WordPress plugin through version 1.0.1 does not perform a nonce or capability check in an AJAX action that updates navigation menu item metadata. This allows any authenticated user, including Subscribers, to overwrite menu item content and settings that are rendered in the site's public navigation.

The Charitable WordPress plugin before version 1.8.5.3 does not sanitize and escape one of its campaign image text fields before outputting it in an HTML attribute. This allows users with high-privilege campaign-management roles to perform Stored Cross-Site Scripting (XSS) attacks that execute on the front-end campaign page.

A vulnerability in keras-team/keras versions <= 3.14.0 allows arbitrary local HDF5 file content disclosure due to improper handling of HDF5 ExternalLinks. The `KerasFileEditor` and `keras.saving.load_weights` functions bypass the `safe_get_h5_group` and `safe_get_h5_dataset` helpers, which are designed to reject ExternalLinks and SoftLinks. This results in automatic dereferencing of links to external HDF5 files, enabling attackers to disclose sensitive data from the victim's local filesystem.

guzzlehttp/guzzle before version 7.15.1 fails to preserve host-only cookie scope, storing the request host in the Domain field instead of marking cookies as host-only. Attackers controlling child hosts can receive host-only cookies intended only for parent hosts, potentially disclosing session identifiers and authorization tokens.

guzzlehttp/guzzle before version 7.15.1 contains an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment from the referring request into the Referer header during a redirect. An attacker controlling the redirect destination can read this fragment, potentially disclosing one-time login secrets, access tokens, and other sensitive data.

guzzlehttp/guzzle before version 7.15.1 contains a denial of service vulnerability in the CookieJar that accepts unlimited Set-Cookie header fields with no size restrictions. Attackers can return many large cookies from a malicious server, causing Guzzle to store excessive data in memory and generate oversized Cookie headers that fail in handlers or destination servers.

ArcadeDB before version 26.7.2 fails to enforce the UPDATE_SCHEMA database permission on the ALTER TYPE ... CUSTOM and ALTER TYPE ... BUCKETSELECTIONSTRATEGY SQL operations. An authenticated user with read-only access can submit these statements via the HTTP command endpoint to mutate schema metadata and bucket-selection strategy, bypassing the updateSchema permission boundary.

GuzzleHttp before version 7.14.2 fails to properly isolate Proxy-Authorization headers from origin servers in cURL handlers. Attackers can capture proxy credentials through origin server access logs when requests are redirected, bypassed, or sent through SOCKS proxies that Guzzle misclassifies as direct connections.

JupyterLab before version 4.5.9 contains a stored cross-site scripting vulnerability in the Extension Manager that fails to validate URI protocols in package metadata URLs. Attackers can publish malicious PyPI packages with javascript: URLs in project metadata that execute arbitrary JavaScript in the JupyterLab origin when users click the extension name.

Better-auth before version 1.4.9 contains a two-factor authentication bypass vulnerability when session.cookieCache is enabled. Attackers with valid primary credentials can access authenticated routes without completing second-factor verification by exploiting premature session caching.

Better-auth before version 1.6.2 fails to validate the OAuth state parameter against the stored nonce when using cookie-backed state storage without PKCE. Attackers can forge the state parameter and supply an attacker-controlled authorization code to create authenticated sessions bound to the attacker's external identity or persistently link attacker accounts to victim profiles.

@better-auth/oauth-provider before version 1.7.0-beta.4 fails to bind access-token audience to the authorization grant, allowing clients to request tokens for unrelated resources. Attackers can complete an OAuth flow and obtain access tokens whose audience targets resource servers the authorization never covered, bypassing intended authorization boundaries.

Axios versions >=1.13.0 (Node.js HTTP adapter) fail to enforce the configured maxBodyLength limit on streamed request bodies when requests are sent with httpVersion: 2. Because Node's HTTP/2 request API does not honor the maxBodyLength option and axios's byte-counting stream wrapper is gated on maxRedirects === 0, an attacker who controls a stream passed to axios can cause the application to transmit outbound data exceeding the configured finite maxBodyLength. Impact is limited to resource consumption and policy bypass (excess egress, upstream quota consumption, limited availability); it does not enable code execution, credential disclosure, or request-destination control. Calls using the default maxBodyLength: -1 and browser adapters are not affected.