Booster for WooCommerce Flaw: What To Do Now
If your WooCommerce store runs the Booster for WooCommerce plugin at version 8.4.0 or older, update it today if a newer version with a security fix is available, or deactivate and delete it if not, because it has a critical flaw (CVE-2026-42718) that an attacker can reach without logging in.
This post is for store owners, freelancers and agencies who run WooCommerce and are not security specialists. You will learn what the flaw is in plain English, how to check if you are affected, the exact steps to fix it, and how to check that nothing bad happened in the meantime.
What happened
A vulnerability was published for the Booster for WooCommerce plugin and given the ID CVE-2026-42718. A CVE is a public ID number that lets everyone refer to the same security bug. The record was published on the National Vulnerability Database (NVD) on 2026-10-10.
The NVD describes it as an unauthenticated PHP Object Injection in Booster for WooCommerce versions up to and including 8.4.0. "Unauthenticated" means the attacker does not need an account on your site. NVD marks it Deferred, meaning NVD has not prioritized its own analysis of the entry. The 9.8 score and the details come from the record as published, not from an NVD review. The plugin research firm Patchstack also lists the issue in its vulnerability database.
We are not repeating any technical exploit details here, and the source record does not give us any. We also have no information in the record about whether attackers are using this flaw in the wild. Treat it as serious and fix it quickly, without panic.
The key facts at a glance
| Item | What the source says |
|---|---|
| Plugin | Booster for WooCommerce |
| CVE ID | CVE-2026-42718 |
| Affected versions | 8.4.0 and earlier (taken from the description) |
| Flaw type | PHP Object Injection (CWE-502) |
| Login needed to attack? | No (unauthenticated) |
| Severity | Critical, CVSS 9.8 |
| NVD publish date | 2026-10-10 |
| Fixed version | Not listed in the NVD record |
Because the NVD record does not name a fixed version, the safe advice is simple: install the newest version available and read the plugin's changelog (the list of changes on its WordPress.org page, under the "Changelog" or "Development" tab) to confirm the security fix is mentioned. If it is not mentioned, see Step 2.
What "PHP Object Injection" means in plain English
WordPress and WooCommerce are written in a language called PHP. Plugins sometimes need to save a complex piece of data as plain text and rebuild it later. That process is called serialization (saving) and deserialization (rebuilding).
The trouble starts when a plugin rebuilds data that came from a visitor without checking it first. An attacker can then hand the site a specially crafted piece of data, and the site may rebuild it into something the developer never intended. OWASP explains this class of bug in detail. It is also tracked as CWE-502, "Deserialization of Untrusted Data".
How bad the result is depends on what other code is installed on the site. In some setups the outcome can be limited. In others it can lead to things like file changes or full site takeover. We cannot say which applies to your store, which is a good reason to act rather than gamble.
Why the score is 9.8 out of 10
The CVSS score is an industry-standard way to rate how severe a bug is. The vector for this one is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Here is what each part means:
- AV:N means it can be attacked over the internet.
- AC:L means the attack is not complicated.
- PR:N means the attacker needs no account or privileges.
- UI:N means no one has to click anything.
- C:H / I:H / A:H means the possible impact on confidentiality (data leaks), integrity (data changes) and availability (site going down) is rated high.
In short, a bug that anyone can reach without logging in, with a high possible impact, scores near the top. That is why it matters even for a small store with no famous name.
Step 1: Find out if you use Booster and which version
Log in to your WordPress dashboard and go to Plugins > Installed Plugins. Look for "Booster for WooCommerce." The version number is shown under the plugin name.
If you have command line access and WP-CLI installed, you can check with:
wp plugin get woocommerce-jetpack --fields=name,version,status
The plugin's folder name is woocommerce-jetpack, which is a leftover from its earlier name. If the command says the plugin is not installed under that folder name, check Plugins > Installed Plugins by eye for a Booster edition, since a paid edition may use a different folder name.
If you use a paid Booster edition (such as Booster Plus), do not assume you are safe or affected. Check the vendor's changelog and support page for that edition and update it too.
Step 2: Back up, then update
Take a backup first. Use your host's backup tool or a backup plugin. If your store takes orders all day, a database backup is the most important part.
Then update:
- Go to Dashboard > Updates or Plugins > Installed Plugins.
- Click Update now under Booster for WooCommerce.
- Open the plugin's changelog and check that the version you installed is newer than 8.4.0 and that the changelog confirms a security fix.
- Visit your shop, add a product to the cart and open the checkout page to confirm nothing broke.
If the newest available version is still 8.4.0 or older, or the changelog does not mention a security fix, treat the plugin as unpatched: deactivate and delete it until the vendor confirms a fix.
With WP-CLI, the update command is:
wp plugin update woocommerce-jetpack
If you manage many stores, update them one at a time and test each one. Do not push the update everywhere at once without a quick check.
If you cannot update right now
Sometimes a custom setup or a conflict with another plugin stops you from updating. In that case, the safest short-term move is to deactivate and, if you can, delete the plugin until you can update. Go to Plugins > Installed Plugins, click Deactivate, then Delete.
If the newest version is still 8.4.0 or older, or the changelog does not mention a security fix, treat the plugin as unpatched. Deactivate and delete it until the vendor confirms a fix.
Be aware that Booster adds many extra features to WooCommerce, so some of your store's custom pricing, labels or documents may stop working. Note the settings you rely on before you remove it. Losing a feature for a day is a far smaller problem than a compromised store.
Step 3: Check for signs of trouble
Once you are on a version whose changelog confirms a fix for this issue, updating closes the door going forward. It does not tell you whether someone already walked through it. The NVD record was published in October, so a store that stayed on an old version for weeks deserves a quick check. Run through this list:
- [ ] Open Users > All Users and filter by Administrator. Remove any admin you do not recognize.
- [ ] Check WooCommerce > Orders and WooCommerce > Settings > Payments for changes you did not make, such as altered payout or payment details.
- [ ] Look for unfamiliar plugins or themes under Plugins and Appearance > Themes.
- [ ] Ask your host if they can show recent file changes or unusual traffic in the access logs.
- [ ] Search Google for
site:yourdomain.comand look for pages or spam you did not create.
If you have WP-CLI, you can run these three commands. The first two commands compare files against the official copies. The third lists admin users so you can spot unknown ones.
wp core verify-checksums
wp plugin verify-checksums --all
wp user list --role=administrator
Note that wp plugin verify-checksums only works for plugins from WordPress.org. Paid or custom plugins cannot be checked this way.
A mismatch is not always an attack, since some plugins ship files that differ. Treat it as a reason to look closer. If something looks wrong, change your admin, hosting and database passwords, then follow our guide for a hacked website. If you change the database password, update it in wp-config.php too, or get your host to do it. Otherwise the site will go offline. It also helps to reset the WordPress security keys (salts) in wp-config.php, which logs out everyone who is currently signed in.
Make the next plugin flaw less painful
Plugin bugs like this one are a normal part of running WordPress. You cannot stop them from being found. You can shorten the time between a fix and your update. A few habits help:
- Turn on automatic updates for plugins you trust, under Plugins > Installed Plugins, using the "Enable auto-updates" link next to each one.
- Delete plugins you no longer use. An inactive plugin can still be a risk if its files are on the server.
- Keep off-site backups and test that you can restore them.
- Use unique admin passwords and turn on two-factor login for every admin.
- Keep a short list of every plugin on every store you manage, so you know who to alert when news like this appears.
A good first look at your public setup is our free website security check. You can also read how hackable your site really is to see which problems are common on small business sites.
Key takeaways
- Booster for WooCommerce 8.4.0 and earlier is affected by CVE-2026-42718, a critical (CVSS 9.8) unauthenticated PHP Object Injection flaw.
- Update to the newest version today, after a quick backup, and read the changelog because the NVD record lists no fixed version.
- If the newest version is still 8.4.0 or older, the changelog does not mention a security fix, or you cannot update, treat the plugin as unpatched. Deactivate and delete it until the vendor confirms a fix.
- After updating, check for unknown admin users, odd file changes and altered payment settings.
- Turn on auto-updates, remove unused plugins and keep tested backups to shorten your exposure next time.
Want a human to look at your store?
A patch fixes one known bug. It cannot tell you what else is exposed on your site. A Bug Circuit Circuit audit is $49 one time. A real security engineer manually tests your site and sends a written report with every issue, its severity, the evidence and the exact fix. It is a focused audit for small sites, not an enterprise pentest or a compliance certificate. See the pricing page if you want to know what is included.
A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.
See pricing