Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-39750 Overview
CVE-2026-39750 is an unauthenticated reflected Cross-Site Scripting (XSS) vulnerability in the StoreGrowth: Smart Sales Booster for WooCommerce WordPress plugin. The flaw affects versions 2.0.6 and earlier of the plugin, which provides BOGO offers, upsells, direct checkout, quick view, and side cart functionality for WooCommerce stores. An unauthenticated attacker can craft a malicious URL or input that, when processed by a victim's browser, executes arbitrary JavaScript in the context of the affected site. The vulnerability is tracked under CWE-79: Improper Neutralization of Input During Web Page Generation.
Critical Impact
Unauthenticated attackers can execute arbitrary JavaScript in a victim's browser, enabling session theft, administrative account takeover, and content manipulation on affected WooCommerce stores.
Affected Products
- StoreGrowth: Smart Sales Booster for WooCommerce (plugin slug storegrowth-sales-booster)
- All versions <= 2.0.6
- WordPress sites running WooCommerce with the affected plugin installed
Discovery Timeline
- 2026-10-06 - CVE-2026-39750 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-39750
Vulnerability Analysis
The vulnerability is a reflected Cross-Site Scripting (XSS) issue classified under CWE-79. User-supplied input is incorporated into HTML output without proper neutralization. Because exploitation requires no authentication, any visitor-triggered request path exposed by the plugin can serve as an entry point.
The CVSS vector indicates a changed scope, meaning that successful exploitation impacts resources beyond the vulnerable component. In practice, injected scripts execute in the browser context of any user who follows a crafted link or loads an attacker-influenced page element. User interaction is required, typically through a victim clicking a malicious link.
The EPSS probability sits at approximately 0.237% as of 2026-10-07, placing exploitation likelihood in the lower range of observed vulnerabilities. However, WordPress plugin XSS issues are commonly weaponized in opportunistic campaigns targeting e-commerce storefronts.
Root Cause
The root cause is improper neutralization of input during web page generation. The plugin accepts data from HTTP request parameters and reflects that data into rendered HTML or JavaScript contexts without applying appropriate escaping functions such as esc_html(), esc_attr(), or esc_js(). The absence of context-aware output encoding allows attacker-controlled markup, including <script> tags and event handlers, to execute in the victim's browser.
Attack Vector
Exploitation occurs over the network with low attack complexity and no privileges required. An attacker crafts a URL containing a malicious payload targeting a vulnerable parameter in the StoreGrowth plugin. The attacker then delivers that URL to a victim through phishing, forum posts, or social engineering. When the victim loads the URL on the vulnerable WooCommerce site, the injected script executes with the privileges of the victim's session.
If the victim holds administrator privileges, the attacker can hijack the session, create rogue admin accounts, inject malicious plugins, or modify checkout flows to skim payment data from customers. Refer to the Patchstack vulnerability report for technical disclosure details.
Detection Methods for CVE-2026-39750
Indicators of Compromise
- Web server access logs containing requests with HTML/JavaScript payloads such as <script>, onerror=, onload=, or javascript: targeting plugin endpoints under /wp-content/plugins/storegrowth-sales-booster/
- Unexpected creation of WordPress administrator accounts or modifications to the wp_users and wp_usermeta tables
- Unauthorized changes to plugin, theme, or checkout files following suspicious inbound traffic to StoreGrowth plugin URLs
- Outbound requests from administrator sessions to unknown third-party domains, indicating cookie or token exfiltration
Detection Strategies
- Inspect HTTP request parameters for URL-encoded script tags, event handler attributes, and known XSS payload patterns targeting the plugin
- Correlate inbound traffic to StoreGrowth plugin paths with subsequent administrative actions in WordPress audit logs
- Deploy a Web Application Firewall (WAF) with signatures for reflected XSS attempts against WordPress plugins
Monitoring Recommendations
- Enable WordPress audit logging to capture user creation, role changes, and plugin modifications
- Monitor Content Security Policy (CSP) violation reports to surface attempted script injections
- Alert on anomalous spikes in query string length or special character density on plugin endpoints
How to Mitigate CVE-2026-39750
Immediate Actions Required
- Identify all WordPress sites running the StoreGrowth: Smart Sales Booster for WooCommerce plugin at version 2.0.6 or earlier
- Deactivate the plugin until a patched version is installed if active exploitation attempts are observed
- Rotate administrator passwords and invalidate active sessions on any site suspected of exposure
- Enable multi-factor authentication for all administrative WordPress accounts to limit the impact of session hijacking
Patch Information
At the time of publication, consult the Patchstack advisory and the vendor's WordPress plugin page for the latest fixed release. Upgrade to a version later than 2.0.6 as soon as the vendor publishes a patch. Verify the installed version through the WordPress admin dashboard under Plugins.
Workarounds
- Deploy a WAF rule to block requests containing XSS payloads directed at /wp-content/plugins/storegrowth-sales-booster/ paths
- Apply a strict Content Security Policy that disallows inline scripts and restricts script sources to trusted origins
- Restrict administrative access to the WordPress backend by IP allowlist where feasible
- Temporarily disable the plugin on high-value e-commerce sites until a verified patch is applied
# Example Nginx rule to block common XSS payloads targeting the plugin
location ~* /wp-content/plugins/storegrowth-sales-booster/ {
if ($args ~* "(<|%3C)script|onerror=|onload=|javascript:") {
return 403;
}
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

