Atomic Edge analysis of CVE-2026-19088: The ShopEngine plugin for WordPress (versions up to and including 4.9.2) is vulnerable to Cross-Site Request Forgery (CSRF) due to missing nonce validation on a function. The vulnerability resides in the plugin’s onboarding functionality, specifically in the `core/onboard/onboard.php` file, which processes user onboarding data. An attacker can forge a request to this endpoint, tricking a site administrator into performing actions such as submitting their email address or other data without their consent. This can lead to unauthorized data collection and potential privacy violations. The CVSS score is 4.3 (Medium), indicating a moderate risk.
Root Cause: The root cause of the vulnerability is the absence of nonce verification in the onboarding handler function. In `shopengine/core/onboard/onboard.php`, the function that handles onboarding data (likely an AJAX action) processes the `$data` array, extracts the email address from `$data[‘user_onboard_data’][’email’]`, sanitizes it, and sends it to the plugin’s data collection service via `Plugin_Data_Sender::instance()->sendEmailSubscribeData()`. Before the patch, there was no call to `check_ajax_referer()` or `wp_verify_nonce()`, and no capability check (`current_user_can(‘manage_options’)`) was performed on this specific request. This allows an attacker to craft a request that, when triggered by an authenticated administrator (for example, by visiting a malicious page or clicking a link), will execute the onboarding process. The patch adds nonce verification and capability checks in the new `Auto_Install_Notice` class, but the original onboarding function in `onboard.php` still lacks these protections as per the diff. However, the diff also shows changes to `core/settings/action.php` and new auto-install notice functionality, indicating that the vulnerability was addressed by introducing a more secure onboarding flow that includes nonce checks and permission validation in the new code. The root cause is the lack of CSRF protections in the original onboarding handler, which the patch mitigates by implementing nonce verification and capability checks in the new `Auto_Install_Notice` handlers (`handle_dismiss` and `handle_confirm`).
Exploitation: An attacker can exploit this vulnerability by crafting a malicious request to the WordPress admin-ajax.php endpoint or a direct POST to the plugin’s onboarding endpoint. The exact action name is not specified in the diff, but based on the code, it likely uses an AJAX action such as `shopengine_onboard` or similar. The attacker would create a form or a link that submits a POST request with parameters like `action=shopengine_onboard` and `user_onboard_data[email]=attacker@example.com`. When an authenticated administrator visits a page containing this request (e.g., via a CSRF attack using an image tag or a hidden form), the administrator’s browser sends the request with their cookies, causing the plugin to process the onboarding data and send the email to the attacker-controlled address. The attacker can also include other fields as needed. The vulnerability allows unauthenticated attackers to perform actions on behalf of the administrator without their knowledge.
Patch Analysis: The patch introduces several changes to address the CSRF vulnerability. First, in `shopengine/core/onboard/onboard.php`, the onboarding process now updates options `wpmet_onboard_email_collected` and `wpmet_onboard_collected_email` after sending the email, but it still does not add nonce verification to that specific function. However, the patch adds a new class `Auto_Install_Notice` in `shopengine/utils/onboard/auto-install-notice.php` that registers AJAX handlers `handle_dismiss` and `handle_confirm`. Both handlers now call `check_ajax_referer(‘shopengine_auto_install_notice_nonce’, ‘nonce’)` and verify user capabilities with `current_user_can(‘manage_options’)`, ensuring that the request is legitimate. The patch also modifies `core/settings/action.php` to skip onboarding if the plugin was silently installed, and introduces `Auto_Install_Tracker` to mark plugins as auto-installed. These changes collectively ensure that onboarding actions require a valid nonce, thereby preventing CSRF attacks. The before behavior allowed any request to trigger onboarding without validation; after the patch, the new handlers enforce nonce and capability checks, making forgery infeasible.
Impact: If exploited, this vulnerability allows an attacker to perform unauthorized actions on behalf of a site administrator, specifically the submission of the administrator’s email address to the plugin’s data collection service. This could lead to the administrator receiving unsolicited emails, privacy violations, and potential phishing attacks if the collected email is used maliciously. Additionally, the attacker could potentially trigger other onboarding steps, such as installing or activating plugins, by crafting requests to other endpoints that lack nonce validation. The impact is limited to actions that the onboarding process can perform, which may include modifying plugin settings, installing recommended plugins, or collecting site data. However, the primary consequence is the unauthorized collection and transmission of the administrator’s email address, which can be used for spam or social engineering.







