Attacks reportedCVE published · 22 Sep 2026
WPC Product Bundles for WooCommerce
CVE-2026-93836 Severity · High
CVSS 7.2
Affected
All versions up to and including 8.6.6
Fixed in
8.6.7 (latest release: 8.7.7)

CVE alert · WordPress

CVE-2026-93836: WPC Product Bundles lets anyone hide a script that runs when staff open an order

Anyone, with no account, can hide a script in a store order through WPC Product Bundles for WooCommerce 8.6.6 or older. The script can take over the site when an administrator opens that order. Update to 8.6.7 or later, then check for hidden admin accounts.

Check your systems with your AI agent

Paste this prompt into an AI agent that can run commands on your machines. It only reads versions and settings, asks before using administrator rights, and ends with a report.

Check whether my systems are affected by CVE-2026-93836 in WPC Product Bundles for WooCommerce, then write me a report.

Read the alert first: https://securityaudit.ae/cve/cve-2026-93836-wpc-product-bundles/

What the alert says (facts checked 23 October 2026):
- Affected: All versions up to and including 8.6.6
- Fixed in: 8.6.7 (latest release: 8.7.7)
- Exploited: Yes: Patchstack reports attacks since 4 October 2026; not in CISA's KEV catalog as of 23 October 2026

Rules:
- Read only. Do not install, update, restart, delete or change anything, and never run exploit or proof-of-concept code.
- Run only commands that read versions or settings. Ask me before any command that needs sudo or administrator rights.
- If you do not know which machines, containers, cloud accounts or sites are in scope, ask me for the list before you start.
- If a machine cannot be reached or a command fails, say so. Do not guess.

Steps:
1. Find where WPC Product Bundles for WooCommerce runs: servers, containers and their hosts, cloud services, sites.
2. On each one, read the installed version and the settings the alert names. The alert gives these commands:

    wp plugin get woo-product-bundle --field=version

3. Compare each version with the affected and fixed versions above. When a vendor or a distribution ships its own fixed package, the alert names it.
4. Report: one line per machine or service with the version found, Affected, Not affected or Unknown, and the evidence (the command and its output). Then the actions to take, in order, from the alert's "How to fix" section, and what you could not check.

Key facts

FactDetail
ProductWPC Product Bundles for WooCommerce (WordPress plugin)
Affected versionsAll versions up to and including 8.6.6
Fixed in8.6.7 (latest release: 8.7.7)
Severity7.2 High (CVSS 3.1, Wordfence)
Who can attackAnyone over the internet, no login needed; the admin takeover needs a logged-in administrator to open the order
ExploitedYes: Patchstack reports attacks since 4 October 2026; not in CISA's KEV catalog as of 23 October 2026
CVE published22 September 2026

What an attacker can do

The plugin lets a store sell several products as one bundle, and each bundled item has a quantity value named qty. Before 8.6.7, the plugin only checked that this value turned into a number. Text that starts with a number, such as 1<script ...>, passed that check. The plugin saved this text in the order, then printed it as live code (stored cross-site scripting, or XSS).

The code runs when staff open the order in wp-admin (the WordPress admin area), and it acts with their login. Patchstack analyzed the script used in real attacks on this flaw. One successful run installs:

  • a malicious plugin, WP Smart Thumbnails
  • a new administrator account
  • a hidden administrator that wp-admin does not list
  • a backdoor login URL that signs in as the oldest administrator
  • a file manager that needs no login

The attacker controls the store and its customer data, even if you remove the vulnerable plugin.

Who is affected

Every site that runs WPC Product Bundles for WooCommerce version 8.6.6 or older is affected. WordPress.org counts more than 30,000 active installs.

The store must sell bundle products. The attacker puts the script in a bundle request to a product URL, and the store saves it in the order. The CVE record and Wordfence both say the attacker needs no account. Neither says how the attacker places the order: through guest checkout, or with a customer account.

The admin takeover happens when a logged-in administrator opens that order in wp-admin. If the setting "Hide bundled products on order details" is set to one of the two "Yes, but ... list bundled sub-product names under the main bundle" options, the same script also prints on the order confirmation page and in order emails. The default ("No") does not print it there.

How to check your version

With WP-CLI (the WordPress command-line tool), run this on the server:

shell
wp plugin get woo-product-bundle --field=version

Without WP-CLI, open wp-admin > Plugins > Installed Plugins and read the version on the "WPC Product Bundles for WooCommerce" row. Version 8.6.6 or older is vulnerable.

If the site ran a vulnerable version at any time, also run the attack checks in the next section.

What to do now

Update the plugin today, to the latest release (8.7.7) if you can. Every version from 8.6.7 fixes this flaw. With WP-CLI:

shell
wp plugin update woo-product-bundle

The update alone does not remove backdoors from an earlier attack, so look for the signs Patchstack published:

  • imgcdn1.com in web server, WAF (web application firewall, a filter in front of the site) or proxy logs (the dots stay readable even when the rest of the address is encoded), or woosb_ids together with %3Cscript in a request to a product page. Logs only show attacks sent in the web address and miss form data sent with POST, so a clean log does not prove the site is clean: run the database and file checks below either way.
  • requests to wp-login.php with _wplogin in the web address, or direct requests to wp-smart-thumbnails.php
  • the folder /wp-content/plugins/wp-smart-thumbnails/, with emer-run.php
  • class-wp-token-validate.php or class-wp-query-*.php in /wp-content/mu-plugins/ (plugins WordPress loads automatically)

Patchstack's report also gives two database queries. Before you run them, replace wp_ with your site's table prefix in the table names and in 'wp_capabilities'. The prefix is the $table_prefix value in wp-config.php.

The first query lists every administrator. Look for one missing from the Users screen. Also look for an @wordpress.org email, or a name like support, updater or maintenance:

sql
SELECT u.user_login, u.user_email, u.user_registered FROM wp_users u JOIN wp_usermeta m ON m.user_id = u.ID WHERE m.meta_key = 'wp_capabilities' AND m.meta_value LIKE '%administrator%';

The second looks for two entries that the backdoor writes in the wp_options table. Any row returned means the backdoor is or was on the site:

sql
SELECT option_name FROM wp_options WHERE option_name IN ('fz_emer_done_v1', 'fz_emer_login_tokens');

Do not trust file dates: the attacker's installer backdates its files. If you find a sign, treat the site as compromised. Remove unknown accounts and plugins, the mu-plugins files above and the two fz_emer_ entries. Change every admin password, starting with the oldest administrator's, which the backdoor login uses. Then change the WordPress salts (secret keys behind login cookies).

Is it being exploited?

Yes. Patchstack reports attacks on this flaw, and the earliest request in its data came on 4 October 2026 at 10:39 UTC. The attempts that day used four IP addresses: 204.8.96.109, 147.90.235.22, 90.184.10.74 and 94.16.115.121. The attack code sat in the woosb_ids[...][qty] value and loaded a script from imgcdn1.com/fz/x.js. On 5 October 2026, the attackers sent the same code through another flaw, Ninja Forms CVE-2026-94504. Patchstack published its report on 6 October 2026.

On 23 October 2026, the flaw was not in CISA's KEV catalog (the US list of flaws known to be exploited). The agency's note on this flaw, dated 22 September 2026, says "Exploitation: none"; it predates these attacks.

Get help

Updating closes this flaw. Flaws in your own code get no CVE and no update, and a test of your app is how they are found.

Web app and API security test

A penetration test of your web app and its API: who can see whose data, and what an attacker can change.

From AED 20,000, excl. 5% VAT

Ask for a quote Book a call

Sources

  1. CVE-2026-93836 record CVE Program
  2. WPC Product Bundles for WooCommerce <= 8.6.6 - Unauthenticated Stored Cross-Site Scripting via 'qty' Parameter Wordfence
  3. Four ways back in: the WordPress XSS campaign that hides its own admin account Patchstack
  4. WPC Product Bundles for WooCommerce: changelog (Development tab) WPClever / WordPress.org
  5. CVE-2026-93836 detail NIST National Vulnerability Database
  6. Known Exploited Vulnerabilities Catalog CISA

More CVE alerts

All CVE alerts