HomeWordPress vulnerabilitiesStoreGrowth
StoreGrowth vulnerabilities
StoreGrowth has 5 known vulnerabilities in this database. The most recent published record is dated 6 Oct 2026.
- Known vulnerabilities
- 5
- Active installs
- 2,000+
- Latest version
- 2.2.0
- Last updated
- 19 Aug 2026
- Most recent
- 6 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-39750 | High 7.1 | Up to 2.0.6 | Fixed in a later version (latest 2.2.0) | 1 d ago |
| Broken access control CVE-2026-78137 | High 7.5 | Before 2.1.2 | Fixed in 2.1.2 | 27 Aug 2026 |
| Broken access control CVE-2026-13110 | Medium 5.3 | Up to 2.1.0 | Fixed in a later version (latest 2.2.0) | 28 Jul 2026 |
| Cross-site scripting (XSS) CVE-2026-13440 | High 7.2 | Up to 2.1.0 | Fixed in a later version (latest 2.2.0) | 28 Jul 2026 |
| Broken access control CVE-2026-15411 | Medium 5.3 | Up to 2.1.0 | Fixed in a later version (latest 2.2.0) | 28 Jul 2026 |
Read the published descriptions
- CVE-2026-39750, 6 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in StoreGrowth: Smart Sales Booster for WooCommerce | BOGO, Upsells, Direct Checkout, Quick View, Side Cart <= 2.0.6 versions. CVE record
- CVE-2026-78137, 27 Aug 2026
- The StoreGrowth WordPress plugin before 2.1.2 does not validate a browser-supplied product price on two of its unauthenticated actions, allowing unauthenticated attackers to add a product to the cart at an arbitrary, attacker-chosen price that carries through to the checkout total when the BOGO offer feature is enabled. CVE record
- CVE-2026-13110, 28 Jul 2026
- The Storegrowth Sales Booster plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 2.1.0. This is due to a missing capability check on the bogo_category_msg_create() AJAX handler, which is registered for both authenticated (wp_ajax_) and unauthenticated (wp_ajax_nopriv_) users and only validates a nonce ('ajd_protected') that is emitted publicly via wp_localize_script() on every frontend page through front_scripts() . This makes it possible for unauthenticated attackers to modify the plugin's BOGO category-message configuration stored in the spsg_bogo_general_settings option by reading the nonce from any public page and POSTing attacker-controlled data to admin-ajax. CVE record
- CVE-2026-13440, 28 Jul 2026
- The StoreGrowth: Smart Sales Booster for WooCommerce | BOGO, Upsells, Direct Checkout, Quick View, Side Cart plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'message_popup' parameter in all versions up to, and including, 2.1.0 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. The exploit is possible because the 'ajd_protected' nonce required by the create_popup handler is exposed to all unauthenticated frontend visitors via wp_localize_script under bogo_save_url.ajd_nonce, effectively bypassing the nonce-only access control. CVE record
- CVE-2026-15411, 28 Jul 2026
- The StoreGrowth: Smart Sales Booster for WooCommerce | BOGO, Upsells, Direct Checkout, Quick View, Side Cart plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.1.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to overwrite the spsg_popup_products option with arbitrary attacker-controlled data. The 'ajd_protected' nonce used as the sole gate is exposed to unauthenticated visitors on every frontend page through the BoGo module's wp_localize_script call, rendering it ineffective as an authorization barrier. CVE record
What to do if you run StoreGrowth
If you run StoreGrowth, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new StoreGrowth vulnerabilities
Free. We email you when a new vulnerability is published for StoreGrowth, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.