CVE-2026-13440: StoreGrowth (WordPress plugin) · Cross-site Scripting
Affects StoreGrowth (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 27 Oct 2026, 05:11 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wedevsStoreGrowth – Upsell, BOGO, Quick View, Direct Checkout & Side Cart for WooCommerce | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, users should consider disabling or restricting the vulnerable plugin functionality. Monitoring vendor channels for updates is recommended. Because the vulnerability involves nonce exposure and input sanitization, remediation will likely require an official patch addressing these issues.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/79d4d776-411e-45ec-aff7-23453e686bf2?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.0.5/modules/sales-pop/includes/Ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.1.0/modules/sales-pop/includes/Ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.1.0/modules/bogo/includes/EnqueueScript.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.1.0/modules/sales-pop/assets/js/popup-custom.js (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.0.5/modules/bogo/includes/EnqueueScript.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/storegrowth-sales-booster/tags/2.0.5/modules/sales-pop/assets/js/popup-custom.js (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3619581%40storegrowth-sales-booster&new=3619581%40storegrowth-sales-booster (opens in a new tab)