The Divi theme for WordPress is vulnerable to DOM-Based Stored Cross-Site Scripting via the `image_src` attribute of the `et_pb_video_slider_item` shortcode in all versions up to, and including, 4.27.6. This is due to the `image_src` field not being included in the `$url_options` whitelist (which only contains `url`, `button_link`, `button_url`), so it never receives `esc_url_raw()` at save time. On the server side, the value is rendered into a `data-image` HTML attribute using `esc_attr()`, which encodes double quotes as `"`. However, the client-side JavaScript carousel code in `custom.unified.js` reads this attribute using jQuery's `.data('image')`, which returns the browser-decoded value (with `"` decoded back to `"`). The decoded value is then concatenated directly into an HTML string and injected into the DOM via `jQuery.after()` without re-escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user hovers over the carousel thumbnail.
The Dear Flipbook – PDF Flipbook, 3D Flipbook, PDF embed, PDF viewer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content (class attribute of .dvcss element)' parameter in all versions up to, and including, 2.4.30 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is embedded as a Base64-encoded JSON object in a CSS class name on a Custom HTML block; the frontend parseCSSElements() function decodes it client-side with atob() and JSON.parse() and renders the logo property as raw HTML, meaning no server-side or client-side sanitization intercepts the malicious script before DOM insertion.
MegaParse 0.0.55 contains an unauthenticated server-side request forgery vulnerability in the POST /v1/url endpoint that fetches caller-supplied URLs server-side. Attackers can supply internal service URLs or metadata endpoints without authentication to read their responses directly from the JSON response.
Xinference (affected commit 4a94832, v3.x) contains an unauthenticated arbitrary-path file read vulnerability in the POST /v1/models/llm/auto-register endpoint, which accepts a caller-supplied model_path parameter without authentication or path confinement. The endpoint reads and parses config.json, tokenizer_config.json, and chat_template.jinja files at the supplied path and reflects the parsed content back to the caller, allowing an unauthenticated attacker to probe the server filesystem and extract content of files with those names in any directory.
The 2nestjs npm package is a malicious typosquatting package impersonating the popular nestjs package. Its postinstall script exfiltrates environment variables containing secrets to a remote server and establishes a reverse shell, allowing arbitrary command execution on the installer's machine.
The npm package tailwindcss-3d-styles version 1.2.4 contains malicious code that fetches and executes arbitrary JavaScript from an external HTTP server at runtime. This behavior allows remote code execution within the Node.js process of any consumer importing this package. The package masquerades as a legitimate library by copying the upstream tailwindcss-3d code and appending the malicious dropper functionality.
The tailwind-scrollbar-styles npm package version 4.0.3 contains malicious code embedded in its dist/index.js file. This code executes a base64-encoded payload that queries Ethereum RPC endpoints to retrieve a transaction from a hardcoded Ethereum address. It decodes part of the transaction to obtain a command-and-control (C2) server IP address, fetches and XOR-decodes commands from that server, and executes them via eval and a detached Node.js process. After execution, the malicious code removes itself from the file to evade detection and forensic analysis. This mechanism allows the attacker to dynamically rotate the C2 server by publishing new Ethereum transactions. No patch or remediation information is provided.
The npm package '1nestjs' version 0.0.1 is a typosquatting malicious package that executes code during installation to exfiltrate environment variables and provide a remote shell to an attacker. It collects environment variables with keys matching sensitive patterns and sends them to a remote server, then opens an interactive shell connection to that server.
The npm package '0nestjs' version 0.0.1 is a malicious typosquatting package targeting developers who mistype 'nestjs'. Upon installation, it executes a postinstall script that harvests environment variables containing secrets and sends them to a remote attacker-controlled server. It also establishes a reverse shell connection to the attacker, allowing interactive command execution on the victim's machine.
Waku is the minimal React framework. Prior to version 1.0.0-beta.1, the unstable_redirect() helper exported from waku/router/server (packages/waku/src/router/define-router.tsx:156–161) accepts an arbitrary string and reflects it unchanged into the HTTP Location response header with no URL validation, scheme restriction, or path-only enforcement. Any application that passes user-controlled input to this helper — the natural pattern documented in the JSDoc and official fixtures — is vulnerable to open redirect attacks. An attacker who convinces a victim to click a crafted link can silently redirect the browser to an arbitrary external domain, enabling phishing, credential harvesting, and OAuth token theft. Additionally, scheme-relative URLs (//evil.example/) bypass naive https?://-only allow-list filters that developers might add as ad-hoc mitigations. This issue has been patched in version 1.0.0-beta.1.
Waku is the minimal React framework. Prior to version 1.0.0-beta.1, Waku's RSC request dispatcher invokes server actions without validating the request's Origin (or Sec-Fetch-Site) header. A cross-origin web attacker can therefore cause a victim browser to issue an authenticated POST to a registered server action endpoint using a CORS-safelisted content type (text/plain), which does not trigger a preflight. Any state-mutating server action that the application exposes via 'use server' can be invoked with the victim's cookies attached. This issue has been patched in version 1.0.0-beta.1.
A numeric truncation weakness exists in the JSON parsing component of the MongoDB C++ Driver's BSON library. An actor who controls the text that an embedding application hands to the library's public JSON parsing interface, when that text is very large, can cause the library to read memory beyond the supplied buffer and return it to the caller, to silently accept only part of the input as a complete document, or to terminate the process. No MongoDB server, credentials, or non-default configuration is required; the effect is confined to the process that uses the library.
A security update for Node.js 22 on Red Hat Enterprise Linux 9.6 addresses multiple vulnerabilities including arbitrary code execution, denial of service, server-side request forgery, unauthorized filesystem access, and memory exhaustion. The update fixes issues in components such as SQLite, brace-expansion, ip-address parsing, and HTTP/2 handling. These vulnerabilities could allow attackers to execute arbitrary code, cause crashes, bypass trust boundaries, or exhaust server memory. The update is rated as important by Red Hat Product Security and is available for multiple architectures and Extended Update Support versions.
CVE-2026-84641 is a use-after-free vulnerability in Mozilla Thunderbird triggered by a malicious IMAP server sending a crafted ID response. This flaw can lead to heap-memory disclosure, with heap contents potentially being saved to prefs.js. The issue was fixed in Thunderbird versions 155, 140.15, and 153.2.
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, when parseBody() expands dot-separated form field names into nested objects with dot-notation parsing enabled, it does not limit the nesting depth or the total number of intermediate objects created. Empty segments are preserved, so one deeply dotted field name can encode one nesting level per byte, while a large number of shallowly dotted fields can create the same amplification across a request. A request body within a normal size limit can therefore allocate an object graph far larger than the request after the body has already been accepted. An unauthenticated attacker who can reach an affected endpoint can send concurrent requests that exhaust the JavaScript heap, terminate the server process, and leave the service unavailable until restart. Dot-notation parsing is not enabled by default, and applications using the default behavior are not affected. This issue is fixed in version 4.13.5.
CVE-2026-84218 is a vulnerability in Red Hat AMQ Broker 7 related to Jolokia's JSR-160 proxy functionality. It involves insufficient validation of client-controlled JMX service URLs, allowing bypass of an existing denylist. This flaw permits the use of alternative valid JMX service URL forms, such as ldaps:// schemes or LDAP URLs with non-empty JMX host components, which can lead to server-side request forgery (SSRF), credential forwarding, and potentially remote code execution.
LibreNMS versions through 26.4.0 have a stored cross-site scripting (XSS) vulnerability in the device showconfig page. This occurs because JSON fields returned by the admin-configurable Oxidized integration URL are rendered without proper escaping. An administrator who configures the Oxidized URL to point to a malicious server can cause arbitrary script execution for users viewing the affected page. The vulnerability is fixed in version 26.7.0.
Kirby is an open-source content management system. Prior to 4.9.5 and 5.5.2, depending on the release line, Kirby's media handler in src/Cms/Media.php allowed Kirby\Cms\Media::thumb() to append a path-bearing filename to a validated parent media directory. On nginx, PHP's built-in server, or Apache with AllowEncodedSlashes enabled, a remote attacker could submit encoded slash characters such as %2f in the filename and traverse outside the parent's media directory. Differences between responses for existing and nonexistent thumbnail configurations disclosed whether an arbitrary .json file existed, and a .json file containing a valid filename key could cause the referenced image to be returned and the job file to be deleted. The related file::version path in src/Filesystem/Asset.php also accepted ../ sequences outside the intended index root. This issue is fixed in versions 4.9.5 and 5.5.2.
CVE-2026-14368 is a medium-severity vulnerability in the Zephyr project's LwM2M JSON content formatter. It involves an off-by-one buffer overflow caused by improper boundary checking when copying a JSON string into a fixed-size buffer. This overflow writes a single null byte immediately past the buffer, potentially corrupting adjacent memory and causing data corruption or a crash. The flaw is triggered by a malicious LwM2M server sending a string resource with a length exactly equal to the buffer size during a WRITE operation. The issue is fixed in Zephyr versions 4.3.2 and 4.4.2 by correcting the boundary check to reject strings that exactly match the buffer length.
A vulnerability in iperf3 allows the server to accept unbounded peer-controlled JSON parameters, which can lead to remote denial of service via resource exhaustion. This issue affects Red Hat Enterprise Linux 10 and its extended update support versions. Red Hat has issued a security advisory and released updates to address this vulnerability.