Latvijas Valsts radio un televīzijas centrs (LVRTC)
eParakstītājs 3.0 version 1.10.0-resolute allows an unauthenticated remote
attacker to cause HTTP GET requests from a user's workstation by convincing the
user to open a crafted signed eDOC file. Automatic certificate validation
retrieves a signer-controlled Authority Information Access (AIA) caIssuers URL
and follows redirects without restricting the destination, enabling blind SSRF
to loopback and private-network services. Additionally, unrestricted loading of
local file URIs (such as file:///dev/zero) causes unbounded memory buffering
resulting in Denial of Service (OutOfMemoryError). In automated server
verification pipelines with UI:N, impact scales up to CVSS 8.6 High.
NocoDB before 2026.05.3 contains an account takeover vulnerability that allows invited users to complete other invitees' signups because batch invitations share one token across all recipients. Attackers holding a valid batch invite can submit another invitee's email with the shared non-expiring token to set its password and take over that account, including higher-role ones.
CVE-2026-130683 is a critical path traversal vulnerability in siyuan-note versions before 3.8.10. The application uses an incomplete deny-list for sensitive paths, omitting important shell initialization files and directories. Authenticated administrators can exploit this flaw by calling the /api/file/copyFile endpoint with an absolute path outside the workspace, allowing them to write malicious payloads that execute with user privileges upon the next shell or login. This vulnerability is fixed in version 3.8.10.
SiYuan before 3.8.10 persists a table block's caption attribute into IAL properties without HTML sanitization, causing stored cross-site scripting upon import or sync. Attackers can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context to achieve remote code execution.
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel.
SiYuan from 3.3.0 before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to inject HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. Attackers can share a crafted .sy.zip document whose rendering in the Electron desktop client with nodeIntegration enabled executes Node.js and host OS commands.
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to execute script by storing malicious Attribute View column names rendered unescaped in col.ts. Attackers can inject HTML via addAttributeViewKey, .sy.zip import, or sync, and when a victim adds or duplicates the column, insertAdjacentHTML runs JavaScript with Node.js privileges for desktop code execution.
SiYuan note-taking software versions before 3.8.10 contain a stored cross-site scripting (XSS) vulnerability in the genAVValueHTML() function. This flaw allows attackers who can store Attribute View asset values to inject malicious scripts via an unescaped image src attribute. The injected script can include a double quote and an onerror handler that executes operating system commands through Node.js when a user opens the affected note or attribute panel in the desktop application. This vulnerability is critical and has been fixed in version 3.8.10.
Parse Server versions before 8.6.119 and 9.x before 9.10.8-alpha.3 have a missing authorization vulnerability. This flaw allows LiveQuery clients without the master key to subscribe to installation and internal classes. Exploiting this, attackers can access installation IDs and device tokens of other devices and modify installations to redirect push notifications.
The Delivery & Pickup Date Time for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 1.3.90. This is due to a nonce-only settings AJAX handler that stores an attribute-breaking value and an administrator settings template that outputs it without HTML attribute escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
The User Frontend – Membership, User Registration, User Profile, User Directory & Content Restriction with Frontend Post Submission plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.3.14 via the `draft_post()` function. This is due to the function storing the `post_content` parameter via `wp_insert_post()` without the protected-shortcode allow-list check that was introduced in 4.3.14 for the sibling `submit_post()` handler — a gap that `wp_kses` filtering does not close, as it strips only HTML tags while leaving shortcode text such as `[wpuf-registration role="editor"]` intact. This makes it possible for authenticated attackers, with Author-level access and above, to embed a registration shortcode in a post and cause any site visitor who subsequently registers through the rendered form to receive Editor-level access. The render-time `wpuf_modify_shortcodes` filter that is designed to neutralize protected shortcodes provides no protection here because posts created via the `wpuf_draft_post` AJAX endpoint carry no `_edit_last` post meta, causing the filter to return the content unchanged and allowing the shortcode to render and execute fully.
The FancyBox for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Anchor 'href' Attribute in all versions up to, and including, 3.4.2 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. Exploitation requires the attacker to wrap the payload anchor around a smilie shortcode (e.g., :mrgreen:), which WordPress renders as an <img> element, satisfying the plugin's a:has(img) enrollment selector and disguising the malicious link as an ordinary comment emoticon.
The GamiPress – Gamification plugin to reward points, badges & ranks in WordPress, now with AI plugin for WordPress is vulnerable to generic SQL Injection via the 'name-1[compare]' parameter in all versions up to, and including, 8.1.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires that an administrator has published at least one GamiPress achievement step triggered by a Forminator field-value submission event, as the GamiPress Forminator integration listener is the only path that routes a form submission's raw field array — including the attacker-controlled compare operator — into gamipress_query_logs().
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 5.3.3. The vulnerability exists because the `matches_mcp_endpoint()` function applies an unanchored regular expression (`#/(?:woocommerce|dokan)/mcp(?:/|$)#`) against the entire `REQUEST_URI` including the query string, meaning any request that contains the literal substring `/dokan/mcp/` or `/woocommerce/mcp/` anywhere in its URI — including inside a query parameter value — is incorrectly treated as a trusted internal MCP context, causing `scope_product_permissions()` to unconditionally return `true` on WooCommerce's `woocommerce_rest_check_permissions` filter regardless of whether the caller is authenticated. This makes it possible for unauthenticated attackers to read full authenticated WooCommerce REST product records for any published product — including private underscore-prefixed meta, purchase notes, downloadable file URLs for paid digital products, catalog-hidden products, and edit-context representations — across the `/wc/v1`, `/wc/v2`, `/wc/v3`, and `/wc-analytics` REST namespaces. The bypass is triggered by appending a query parameter whose value contains the literal string `/dokan/mcp/` to any WooCommerce REST product endpoint (e.g., `/wp-json/wc/v3/products/{id}?x=/dokan/mcp/`); note that percent-encoding the slashes prevents the bypass, as the unencoded literal slash characters are required for the regex to match.
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 Orbit Fox: Duplicate Page, Menu Icons, SVG Support, Cookie Notice, Custom Fonts & More plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'title (post_title)' parameter in all versions up to, and including, 3.0.13 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit is further enabled by wptexturize deliberately skipping texturization of content inside <code> elements and the default WordPress kses allow-list preserving <code> tags and raw double quotes on save, allowing a crafted title attribute breakout payload to survive storage and the the_title filter chain intact.
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-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 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.