Ronnachai Chaipha

**Name of the Vulnerable Software and Affected Versions** Planyo Online Reservation System plugin for WordPress versions prior to 3.1 **Description** An unauthenticated Server-Side Request Forgery (SSRF) exists that leads to Local File Inclusion (LFI). The `ulap.php` file functions as an AJAX proxy and is accessible without authentication. The `send http post()` function checks the host of a provided URL against an allowlist containing 'localhost' but does not validate the URL scheme. This allows an attacker to use the `file://` protocol to bypass the host check, as `parse url()` identifies the host as 'localhost'. The URL is then processed by `curl init()` or `fopen()`, enabling the reading of arbitrary local files such as `/etc/passwd` and `wp-config.php` via the HTTP response. **Recommendations** Update the Planyo Online Reservation System plugin for WordPress to a version newer than 3.0. As a temporary mitigation, restrict access to the `ulap.php` file.

The Shortcodely plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'widget area' parameter in all versions up to, and including, 1.0.1 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.

**Name of the Vulnerable Software and Affected Versions** Logtivity versions prior to 3.3.7 **Description** A logic flaw in the `verifyAuthorization()` function allows unauthenticated attackers to bypass authentication checks. Requests that omit the Authorization header skip Bearer token validation and trigger an unconditional return true statement. This enables unauthorized access to the '/wp-json/logtivity/v1/options' REST API endpoint, allowing the retrieval of plugin configuration options, including the `logtivity site api key` variable, which can be used to impersonate the site in API calls to the Logtivity service. **Recommendations** Update to a version newer than 3.3.6. Restrict access to the '/wp-json/logtivity/v1/options' endpoint to minimize the risk of information disclosure.

The Accessibly plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the REST API in all versions up to, and including, 3.0.3. The plugin registers REST API endpoints at `/otm-ac/v1/update-widget-options` and `/otm-ac/v1/update-app-config` with the `permission callback` set to ` return true`, which means no authentication or authorization check is performed. The `updateWidgetOptions()` function in `AdminApi.php` accepts user-supplied JSON data and passes it directly to `AccessiblyOptions::updateAppConfig()`, which saves it to the WordPress options table via `update option()` without any sanitization or validation. The stored `widgetSrc` value is later retrieved by `AssetsManager::enqueueFrontendScripts()` and passed directly to `wp enqueue script()` as the script URL, causing it to be rendered as a `<script>` tag on every front-end page. This makes it possible for unauthenticated attackers to inject arbitrary JavaScript that executes for all site visitors by changing the `widgetSrc` option to point to a malicious external script.

**Name of the Vulnerable Software and Affected Versions** Appmax plugin for WordPress versions up to and including 1.0.3 **Description** The software contains a flaw due to a lack of proper input validation in a public REST API webhook endpoint. The endpoint, located at `/webhook-system`, does not implement webhook signature validation, secret verification, or authentication mechanisms to confirm the origin of incoming webhook requests. The plugin processes untrusted data from the `event` and `data` parameters without verifying authenticity. This allows attackers to manipulate WooCommerce orders, including modifying their status (processing, refunded, cancelled, or pending) and creating new orders with arbitrary data. Attackers can also create new WooCommerce products with attacker-controlled details like names, descriptions, and prices, and write arbitrary values to order post metadata by spoofing legitimate webhook events. **Recommendations** Versions prior to 1.0.4 should not be used.

**Name of the Vulnerable Software and Affected Versions** CMS Commander plugin for WordPress versions prior to 2.289 **Description** The CMS Commander plugin for WordPress is susceptible to SQL Injection due to insufficient input validation and query preparation. Specifically, the `or blogname`, `or blogdescription`, and `or admin email` parameters are not adequately sanitized, allowing authenticated attackers with CMS Commander API key access to inject malicious SQL queries into existing database queries during the restore workflow. This could lead to the extraction of sensitive information from the database. **Recommendations** Update the CMS Commander plugin to version 2.289 or later.

**Name of the Vulnerable Software and Affected Versions** REST API TO MiniProgram plugin for WordPress versions through 5.1.2 **Description** The REST API TO MiniProgram plugin for WordPress is susceptible to an Insecure Direct Object Reference issue. The issue stems from insufficient validation within the permission callback (`update user wechatshop info permissions check`), which only confirms the existence of a WordPress user corresponding to the supplied `openid` parameter. However, the `update user wechatshop info` function utilizes a separate `userid` parameter, controlled by the attacker, to modify user metadata without verifying if the `openid` and `userid` relate to the same user. This allows authenticated attackers with Subscriber-level access or higher to alter store-related metadata (storeinfo, storeappid, storename) of arbitrary users through the `userid` parameter in the REST API. The vulnerable **API endpoint** is not explicitly mentioned. The vulnerable parameters are `openid` and `userid`. **Recommendations** Versions prior to and including 5.1.2 should be updated.

**Name of the Vulnerable Software and Affected Versions** Build App Online plugin for WordPress versions prior to 1.0.24 **Description** The Build App Online plugin for WordPress is susceptible to unauthorized access. The plugin registers the `build-app-online-update-vendor-product` API endpoint via `wp ajax nopriv ` without sufficient security measures. Specifically, there are no authentication checks, capability verification, or nonce validation within the `update vendor product()` function. This function accepts a user-supplied post ID and uses `wp update post()` to modify the `post author` field without verifying user permissions. This allows unauthenticated attackers to modify the `post author` of any post to 0, effectively removing the original author. Authenticated attackers can also claim ownership of posts by changing the `post author` to their own user ID. The vulnerable parameter is `post ID`. **Recommendations** Update the Build App Online plugin to version 1.0.24 or later.

**Name of the Vulnerable Software and Affected Versions** RepairBuddy – Repair Shop CRM & Booking Plugin for WordPress versions through 4.1132 **Description** The RepairBuddy plugin for WordPress is susceptible to unauthorized access. The plugin has AJAX handlers that, when used together, permit any authenticated user to change admin-level plugin settings. The `wc rb get fresh nonce()` function, accessible via `wp ajax` and `wp ajax nopriv` hooks, allows users to create a valid WordPress nonce for any action name without capability checks. The `wc rep shop settings submission()` function verifies the nonce (`wcrb main setting nonce`) but does not confirm user capabilities before updating over fifteen plugin options using `update option()`. This allows authenticated attackers with subscriber-level access or higher to modify all plugin configuration settings, including business name, email, logo, menu label, and GDPR settings, by generating a valid nonce and then calling the settings submission handler. **Recommendations** Versions prior to and including 4.1132 should be updated. As a temporary workaround, consider restricting access to the `wc rb get fresh nonce` endpoint. Avoid using the `wcrb main setting nonce` parameter in the `wc rep shop settings submission` function until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Stock Ticker plugin for WordPress versions prior to 3.26.1 **Description** The Stock Ticker plugin for WordPress is susceptible to Stored Cross-Site Scripting through admin settings. Insufficient input sanitization and output escaping allow authenticated attackers with administrator-level permissions or higher to inject arbitrary web scripts into pages. These scripts will execute when a user accesses the injected page. This issue only impacts multi-site installations and those where unfiltered html has been disabled. **Recommendations** Update the Stock Ticker plugin to a version later than 3.26.1.

**Name of the Vulnerable Software and Affected Versions** MailArchiver versions prior to 4.4.0 **Description** The MailArchiver plugin for WordPress is susceptible to Stored Cross-Site Scripting through admin settings. Insufficient input sanitization and output escaping allows authenticated attackers with administrator-level permissions or higher to inject arbitrary web scripts into pages. These scripts execute when a user accesses the injected page. This issue specifically impacts multi-site installations and those where unfiltered html has been disabled. **Recommendations** Update MailArchiver to version 4.4.0 or later.

**Name of the Vulnerable Software and Affected Versions** MailArchiver plugin for WordPress versions prior to 4.5.1 **Description** The MailArchiver plugin for WordPress is susceptible to SQL Injection due to insufficient input validation and query preparation. Specifically, the `logid` parameter is not adequately sanitized, allowing authenticated attackers with Administrator-level access or higher to inject additional SQL queries into existing database queries. This can lead to the extraction of sensitive information from the database. **Recommendations** Update the MailArchiver plugin to version 4.5.1 or later.