The FS Poster - WordPress Social media Auto Poster & Scheduler [Facebook, Instagram, Twitter, Pinterest] plugin for WordPress is vulnerable to missing authorization to Unauthorized Social App Data Modification in all versions up to, and including, 8.0.1 This is due to missing authentication, nonce, and capability checks in the `standardFSApp()` function, which is registered on the `wp` action hook and executes on every frontend page load without any login or permission verification. This makes it possible for unauthenticated attackers to insert arbitrary social network app records into the database, or overwrite the OAuth `client_id` and `client_secret` of existing social network connections, by supplying attacker-controlled values via the `fsp_app_redirect` and `app` GET parameters. An attacker can target a specific existing social app record for credential overwrite by supplying matching `social_network` and `slug` values, requiring no knowledge of internal record IDs, which disrupts scheduled social media posts and forces administrators to re-authenticate their connected accounts.
The SchemaEngine AI – AI Schema Markup, Reviews & Rich Snippets for SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'content/excerpt (REST wp/v2/posts) → stored in post_content/post_excerpt' parameter in all versions up to, and including, 3.1.3 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. A Contributor's entity-encoded payload survives save-time wp_kses filtering verbatim and is only decoded into raw script tags at render time via html_entity_decode(), meaning the injected script executes for every visitor — including authenticated Administrators — once an Editor publishes the post through the standard Contributor workflow.
The HTML Forms – Simple WordPress Forms Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'arbitrary POST parameter NAME (the array key, not the value)' parameter in all versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Script execution does not require the Screen Options panel to be opened — injected attributes on the hidden-column checkboxes fire on page load as soon as the Submissions tab is rendered.
The Asset CleanUp: Page Speed Booster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.4.0.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit succeeds even though wp_kses is applied on save, because the XSS is manufactured post-sanitization by the plugin's regex pass: kses-permitted tags such as <a title> and <code> carry the attacker's marker and terminator strings intact into the rendered HTML buffer, where the plugin's own replacement then corrupts the document structure.
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atts (JSON object, specifically the inner `feed` key)' parameter in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is first stored in the wp_ctf_feed_caches database table and later written into the ctf_cron_report WordPress option by the scheduled ctf_feed_update cron job, meaning execution is deferred until the cron runs and an administrator subsequently loads the Support page.
Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute for Linux allows an unauthenticated
remote attacker to execute arbitrary commands with the privileges of the
current user by convincing the user to open and validate a signed PDF with a
crafted filename and select Open with Adobe Reader. The application embeds the
filename in a sh -c command without neutralizing shell command substitution.
CVE-2026-115684 is a vulnerability in Octopus Tentacle where registration credentials are not properly cleared from environment variables. This flaw allows deployment scripts to potentially access these credentials. The issue affects versions prior to 9.2.4285 and has a medium severity rating with a CVSS 4.0 score of 6.1. A fix is available in version 9.2.4285.
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, using the mosquitto_ctrl utility in interactive shell mode to interact with a malicious server could result in a crash of the utility if the server sent a hostile response.
CVE-2026-115731 is a critical remote code execution vulnerability in Perforce Puppet that allows clients with any CA-signed agent certificate to execute code on the server. The flaw arises from deserialization of untrusted data in Puppet's report processing, enabling malicious payload execution with service user permissions. Exploitation can lead to exposure of the server's certificate-signing key, issuance of trusted certificates by attackers, and unauthorized changes to managed systems. The vulnerability was patched in Puppet Enterprise versions 2026.0.1, 2025.12.1, 2023.8.13, and Puppet Core versions 9.1.3 and 8.22.2. It has been actively exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog.
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, the mosquitto_ctrl utility would crash if attempting to interact with a hostile broker and the broker sent a non-string "error" value.
In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session.
In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information.
This can be mitigated by following the documented requirements for PROXY listeners: It is very important that only trusted proxies are allowed to connect to any listener using the PROXY protocol, and that clients are not allowed to connect to the listener at all.
Eclipse Mosquitto versions 2.0.0 to 2.0.22 and 2.1.0 to 2.1.2 contain a vulnerability where the return values of password hash functions (sha512-pbkdf2 and legacy sha512) are not checked. Due to changes in OpenSSL 4.0, sha512-pbkdf2 hashing fails with the FIPS provider for passwords shorter than 8 characters, causing newly created passwords under 8 characters to match any other password of the same length.
In Eclipse versions 1.5-1.6.13, 2.0.0-2.0.22 and 2.1.0-2.1.2, the client library libmosquitto does not reject Will messages with payloads greater than 65535 bytes when calling `mosquitto_will_set()` or `mosquitto_will_set_v5()`. This results in up to 65535 bytes of uninitialised heap memory being transmitted as the Will.
This can be mitigated by only passing payloads with a maximum length of 65535 bytes.
In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default.
A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1.
For an attack to be executable, the Airlock Gateway needs to have 'Smart Form Protection' (or the corresponding expert settings) enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references. The buffer overflow then happens during the parsing of that HTML response. Such a response can come either from a malicious or compromised backend, or from an otherwise trusted backend that returns attacker-supplied HTML, e.g. an application that stores and serves plain user-provided HTML files.
Successfully exploiting the vulnerability can enable an attacker to perform a DoS attack or, in the worst case, an RCE attack against the Airlock Gateway in front of the affected backend. Compromising the functionality of the Airlock Gateway could in this way also affect the availability and protection of other well-intentioned backends deployed behind the same Gateway.
Zohocorp Manageengine DDI Central builds below 6500 contain an authenticated command injection vulnerability in the Windows DDI Agent's clear_blocked_domains functionality. This flaw allows specially crafted blocked-domain values to execute arbitrary commands on affected Windows systems. The vulnerability has a high severity CVSS score of 9.1, indicating critical impact on confidentiality, integrity, and availability.
ManageEngine DDI Central builds below 6500 contain an authenticated PowerShell command injection vulnerability in the Telnet connectivity feature. This flaw allows attackers with valid credentials to execute arbitrary commands on managed Windows nodes by leveraging specially crafted IPv6 scope identifiers. The vulnerability has a high severity with a CVSS score of 9.1, indicating critical impact on confidentiality, integrity, and availability.
Apache SeaTunnel Web 1.0.2 contains an improper authentication vulnerability that allows users with disabled accounts to authenticate successfully and obtain new login tokens. The login process does not verify account status, enabling continued access despite account disabling. This issue requires valid credentials and does not allow credential-free bypass. The product is no longer maintained, and no fixed release exists. Users are advised to discontinue use of this unsupported component.
GNU Emacs version 31.1 contains a code injection vulnerability related to its handling of directory-local variables. A maliciously crafted .dir-locals.el file can include a (REGEXP FUNCTION t) entry in auto-mode-alist that causes Emacs to execute arbitrary Emacs Lisp code with the privileges of the Emacs process when a matching file is opened. This vulnerability does not affect Emacs 30.2.