A flaw has been found in a2ui-project a2ui up to 0.10.6. Affected by this vulnerability is the function DataModel.set of the file renderers/web_core/src/v0_9/state/data-model.ts. Executing a manipulation can lead to resource consumption. It is possible to launch the attack remotely. The exploit has been published and may be used. This patch is called 82789191ce551f4d7a095d273773fb24bd764c9d. A patch should be applied to remediate this issue.
The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to limited media file deletion due to insufficient file path validation in the upload_file function in all versions up to, and including, 3.8.4 This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary media files on the server. This requires the administrator to have enabled the Public API option, and exploitation depends on the hourly cleanup_files task running after the malicious upload.
The All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted Videos plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_fields[embedcode]' parameter in all versions up to, and including, 4.9.7 due to insufficient input sanitization and output 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 sanitization bypass is possible because the save_meta_data() handler returns early when $_POST['post_type'] is absent — a condition always true during XML-RPC requests — and the plugin unconditionally grants Subscribers the publish_aiovg_videos capability, making this exploitable by any authenticated user via a single wp.newPost XML-RPC call.
The affiliate-toolkit – Multi-Network Affiliate & Amazon Product Display plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atkp_product_producturl' parameter in all versions up to, and including, 3.9.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 by unauthenticated attackers requires that the plugin's AJAX loading / AJAX handler option is enabled (atkp_options::get_ajax_loading_enabled() || get_ajax_handler_enabled()) and the attacker knows a product id to render. On a default installation, where that is not configured, the vulnerability requires attackers with contributor-level access and above.
The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'headline-*' Shortcode Attribute in all versions up to, and including, 1.1.17 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. A Subscriber-level user can store a malicious shortcode in their biographical info field; because WordPress core's wp_filter_kses() only strips HTML tags and not shortcode syntax, and because AMP content sanitizers run before do_shortcode() processes the archive description, the synthesized markup is never post-sanitized.
The AI Marketing Expert — AI Email Marketing, AI Content Generator, SEO Analyzer, AI Workflow Automation, Social Media & Ai Chatbot plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 1.2.8 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 only that the chatbot module is active with at least one configured bot; the attacker stores the payload via three unauthenticated REST calls, and the JavaScript widget auto-poll then delivers it to any administrator who opens wp-admin/index.php.
The All-in-One Video Gallery – Video Player & Galleries for YouTube, Vimeo & Self-Hosted Videos plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'more_link' parameter in all versions up to, and including, 4.9.7 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 Pie Register Premium plugin for WordPress is vulnerable to Unrestricted File Type Upload in all versions up to, and including, 3.8.4.0 via the piereg_file_upload function. This is due to the plugin performing file type validation via wp_check_filetype and wp_check_filetype_and_ext but never checking whether those validation calls produced errors before move_uploaded_file() is called, combined with no nonce or capability check on the AJAX handler. This makes it possible for unauthenticated attackers to upload files of dangerous types (e.g. PHP scripts) that may be executable, which makes remote code execution possible. The server returns the generated destination filename in the response, giving the attacker the exact path needed to trigger the uploaded file.
The Ultimate Member – User Profile, Registration, Login, Member Directory, Content Restriction & Membership Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'user_url' parameter in all versions up to, and including, 2.14.0 due to insufficient input sanitization and output 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. Successful exploitation requires a visitor to click the attacker's Website URL link on their public Ultimate Member profile, a condition that is trivially met since the redirect-confirmation onclick handler is enabled by default on all new installations.
GROWI versions 7.0.0 through 8.0.6 have a missing authorization check vulnerability in the collaborative editing feature. This flaw allows users with read-only permissions, including guest users or users with pending, suspended, or invited status, to modify page drafts. The vulnerability has a medium severity rating with a CVSS score of 5.3.
GROWI contains an authorization bypass vulnerability in its tag update and page update APIs. This flaw arises from improper use of a user-controlled key, allowing authenticated attackers to access page contents without having the required read permissions and save them to pages they can edit. The vulnerability affects versions from 4.5.5 through 8.0.6. The CVSS score is 4.2, indicating medium severity.
GROWI contains an authorization bypass vulnerability in its page viewing and commenting functionality. This flaw arises from improper use of a user-controlled key, allowing an authenticated attacker to access page contents and comments without having the necessary read permissions. The vulnerability affects versions from 3.2.10 through 8.0.6. The CVSS score is 4.2, indicating a medium severity level.
Tabularis versions before 0.28.0 have an SQL injection vulnerability in the SQLite driver. This flaw allows malicious clients to execute multiple SQL statements by manipulating the table_name parameter in the describe_table tool. Exploitation can bypass read-only restrictions and write approvals, enabling unauthorized reading, modification, or deletion of SQLite data. The vulnerability is fixed in version 0.28.0.
mews/pos versions up to 2.0.0 have a vulnerability where unauthenticated attackers can forge payment results by submitting unverified callbacks. Specific payment handlers skip critical verification checks, allowing attackers to manipulate order completion without actual payment.
Tencent WeKnora versions from 0.2.11 up to but not including 0.8.2 contain a server-side request forgery (SSRF) vulnerability in the isRestrictedIP() function. This flaw misclassifies NAT64-prefixed IPv6 addresses as public, allowing authenticated attackers to supply URLs that resolve to internal network addresses or cloud metadata endpoints. The vulnerability is fixed in version 0.8.2.
An out-of-bounds write vulnerability exists in llama.cpp versions before b11865 in the ggml-rpc RDMA transport's rdma_recv() function. This flaw allows unauthenticated peers advertising RDMA capabilities to overflow a 1-byte stack variable by sending up to 256 KiB of data, potentially crashing the server or enabling code execution.
LibreSSL versions up to 4.4.0 contain a memory exhaustion vulnerability in the ocspcheck component. This flaw allows malicious OCSP responders to send unbounded HTTP responses, causing the client to consume excessive memory. Attackers who control the OCSP responder or can intercept unencrypted HTTP AIA OCSP traffic can exploit this by streaming endless headers or body data, resulting in denial of certificate status checks.
CVE-2026-118373 is a vulnerability in LibreSSL's ocspcheck component up to version 4.4.0 that causes cleartext transmission of sensitive OCSP request data. The issue arises because the function url2host() removes the OCSP URL scheme, and http_alloc() only uses TLS for port 443. As a result, OCSP requests sent to HTTPS responder URLs on non-443 ports are transmitted without encryption, exposing certificate serial numbers, issuer hashes, and nonces to on-path attackers.
LibreSSL versions up to 4.4.0 contain a CRLF injection vulnerability in the ocspcheck utility. This flaw allows attackers to inject HTTP headers by embedding carriage return and line feed sequences in a certificate's AIA OCSP URI path. The vulnerability arises because the url2host() function copies the path without filtering control characters, and http_open() includes this path in the POST request line, enabling header injection or request splitting to the OCSP responder.