CVE Vulnerability Catalog

Refitter prior to 2.1.2 emits content-type keys from `requestBody/responses` content maps verbatim into a Refit `[Headers(...)]` attribute string without escaping quotation marks. A crafted content-type key in an OpenAPI description can break out of the attribute, interface, and namespace and inject a top-level class with a `[ModuleInitializer]` method that executes attacker code when the generated assembly is loaded. The issue is fixed in version 2.1.2.

Aedes MQTT broker prior to 1.1.1 does not bound topic depth or structural complexity before passing topics through `mqemitter` into `qlobber`. A `PUBLISH`, `SUBSCRIBE`, or registered `Will` message with an excessively deep topic triggers an uncaught `too many words` exception that escapes to the Node.js event loop and terminates the broker process. The issue is fixed in version 1.1.1.

IXP Manager prior to version 7.3.0 allows an authenticated, non-administrative user to elevate privileges to administrator status. Restricting administrative functions reduces exposure but is not a complete fix. The issue is fixed in version 7.3.0.

IXP Manager prior to version 7.3.0 allows an authenticated user to view and edit a resource belonging to another user without authorization. The API-key edit/update path in `ApiKeyController` selects records by identifier without verifying that `user_id` matches the caller. The issue is fixed in version 7.3.0.

In OpenRemote prior to 1.26.0, the datapoint export API constructs CSV crosstab SQL by concatenating asset and attribute names, allowing an authenticated user to inject SQL metacharacters. A crosstab export request can return injected SELECT output in the normal ZIP/CSV response, enabling database exfiltration. In multi-tenant deployments it may expose other tenants' data.

In Netopeer2, a low-privileged authenticated NETCONF user can remotely crash netopeer2-server by sending a get RPC with an invalid subtree filter containing format specifiers. In src/log.c the already formatted buffer is passed to np2log() as the format string, causing vsyslog() to interpret attacker-controlled percent sequences. Denial of service was confirmed on version 2.8.7; reliable remote code execution was not confirmed.

In the refitter dotnet tool prior to 2.1.1, NJsonSchema is invoked with unsafe $ref resolution defaults when generating Refit interfaces from attacker-controlled OpenAPI descriptions. Remote http(s) references cause requests from the developer or CI host and inline untrusted content, while absolute local paths and ../ traversal allow arbitrary local-file disclosure. The chain stops at SSRF, remote file inclusion, and local file inclusion, not code execution.

In LightSAML prior to 4.7.1 and 5.0.1, LightSAML and xmlseclibs disagree about which assertion an inbound SAML signature covers. XMLSecurityDSig::validateReference() removes the enveloped signature from the shared DOM, but processRefNode() resolves Reference URI="#id" document-wide via XPath //*[@Id] and takes item(0), which need not be the assertion whose claims LightSAML consumes. An attacker with a captured genuinely signed assertion can place its signature-stripped bytes in samlp:Extensions and present a forged assertion with the same ID and copied signature, enabling authentication bypass or privilege escalation.

fickling through 0.1.12 incorrectly treats calls to functions from Python standard library modules as safe without inspecting their actual behavior. As a result, check_safety() returns LIKELY_SAFE for malicious pickle payloads that reach code execution or file writes through such callables (e.g., dataclasses._create_fn, mailcap.findmatch, readline.write_history_file). Because fickling.load() uses this verdict as a security gate before pickle.loads(), the payload is deserialized and executed with the privileges of the victim process.

A vulnerability in Trail of Bits fickling through 0.1.12 allows a pickle STACK_GLOBAL operand with a dotted __qualname__ (e.g., "Values.read_file") to be resolved by pickle's find_class via _getattribute to an arbitrary attribute path instead of a module-level function. Fickling records only the leading component in its import tracking and renders the operation as a plain import, so the trailing attribute reference is never analyzed as a call; the OvertlyBadEvals pass does not flag it and check_safety() returns LIKELY_SAFE with zero findings. This lets an attacker reach a class method that performs code execution (optparse.Values.read_file executes exec(open(filename).read(), vars)), achieving arbitrary code execution when the crafted pickle is loaded through fickling.load(), which chains check_safety() into pickle.loads() as an explicit security gate.

The PDF Invoices & Packing Slips for WooCommerce WordPress plugin from 5.16.2 before 5.16.5 does not properly escape several customer-supplied order fields (billing and shipping address values and the customer order note) before outputting them in generated invoice and packing-slip documents. This allows unauthenticated users placing guest orders to store a malicious script that executes when a shop administrator views the document, leading to Stored Cross-Site Scripting.

A stored XSS vulnerability in the Shopper admin panel allows an authenticated staff member with content-upload permissions to store executable HTML or SVG files that are served without Content-Disposition or CSP headers. When an administrator opens such a file, the malicious script executes in their session and can create a new attacker-controlled administrator account with a chosen password. The issue affects versions 2.0.0 through 2.10.0 and 3.0.0-beta.1/beta.2, and is fixed in 2.10.1 and 3.0.0-beta.3.

In Shopper before 2.10.0, the Variants Livewire component in packages/admin/src/Livewire/Components/Products/Form/Variants.php exposes DeleteAction and DeleteBulkAction without server-side authorization. An authenticated staff user with edit_products can obtain the signed component state and permanently delete individual or multiple variants without the delete_product_variants permission. This can destroy the sellable catalogue and disrupt storefront product pages, cart, and checkout. The issue is fixed in version 2.10.0.

In jack before 0.1.0, middleware/handle-error.ts serializes raw FetchError objects into HTTP responses, and lib/servers/base.ts attaches outbound request headers on upstream non-success responses and schema-validation failures. The public extras field in lib/errors/FetchError.ts remains enumerable and is emitted by JSON serialization, exposing internal Radarr/Sonarr X-Api-Key and connector headers such as CF-Access-Client-Secret. The GET /peer/items/:id, GET /servers/health, and GET /torznab/download/:id endpoints can expose these secrets. The issue is fixed in version 0.1.0.

In Dream Displays from 1.5.0 until 1.8.2, user-controlled input can influence arguments passed to yt-dlp under specific conditions. Unintended command-line options may be interpreted by yt-dlp, potentially altering its behavior. The issue is fixed in version 1.8.2.

In ZTNET before 0.8.0, any authenticated low-privilege user can permanently deactivate another account, including an administrator, via POST /api/auth/user/invalidateUser. The handler checks only that a session exists and does not compare session.user.id with the client-supplied userId, so supplying the victim's userId and a non-matching deviceId sets the target account's isActive to false and login is refused. The issue is fixed in version 0.8.0.

ESPAsyncWebServer before version 3.11.2 has a flaw in the multipart parser where it frees a buffer and sets it to NULL but still writes through the NULL pointer. This occurs when the byte after a file part boundary is not a valid terminator, causing a StoreProhibited exception and device reboot. The vulnerability requires a route with file upload or OTA handling.

SABnzbd before version 5.1.0Beta3 allows an attacker with a valid API key to invoke orphan job deletion with a path parameter that is not confined to the download directory. An absolute path can cause recursive deletion of files or directories writable by the SABnzbd process. The API key is stored in plaintext in the configuration file.

libriscv before version 1.18 allows a crafted ELF binary to cause out-of-bounds reads in the host emulator. The serialize_execute_segment and lookup functions trust section offsets and sizes without verifying them against the file size, potentially leading to SIGSEGV or host memory disclosure. The vulnerability is fixed in version 1.18.

Ring before version 1.15.5 has a vulnerability in the wrap-nested-params middleware, which uses a backtracking regular expression to match parameter names. An attacker can craft a parameter name that causes quadratic CPU consumption (O(n^2)), leading to denial of service. Ring-Defaults users are also exposed because the middleware is enabled by default.