In June 2026, backdoored releases of three paid ShapedPlugin plugins went out through the vendor's own update channel. The case is CVE-2026-10735, and one of the three was Product Slider Pro for WooCommerce.

Data collected by Defiant (Wordfence) puts the injection at 21 May and the first customer reports at 10 June. That's about 20 days of stores running the bad code after a normal update.

So the checks below assume an update can be the problem. They take an hour on a staging copy, and Black Friday is Friday, November 27.

1. List every script on the checkout page

WooCommerce redirects an empty cart away from /checkout/, so put a product in a cookie jar first. Replace 123 with a real product ID:

curl -s -c jar.txt -b jar.txt "https://example.com/?add-to-cart=123" -o /dev/null curl -s -b jar.txt "https://example.com/checkout/" \ | grep -oE '<script[^>]+src="[^"]+"' \ | sed -E 's/.*src="([^"]+)".*/\1/' \ | sort -u > checkout-scripts-$(date +%F).txt 

Every line is a host that can read what the buyer types. An old tracking pixel or a chat widget nobody uses any more is still on that list until someone removes it.

This catches the tags in the HTML. Scripts that other scripts inject at runtime only show up in the browser, so open the Network tab in developer tools and place a test order with the JS filter on.

Run the same command again during the sale and diff it:

diff checkout-scripts-2026-11-17.txt checkout-scripts-$(date +%F).txt 

An empty diff is what you want to see.

2. Mark the freeze and watch for file changes

Update core, WooCommerce, the theme and the plugins, then drop a marker file:

touch ~/freeze-$(date +%F) 

From then on, this lists every PHP file written after the freeze:

find wp-content -type f -name '*.php' -newer ~/freeze-2026-11-17 

During a freeze it should print nothing. Pair it with the checksum checks WP-CLI already has:

wp core verify-checksums wp plugin verify-checksums --all 

wp plugin verify-checksums only knows plugins hosted on wordpress.org. A paid plugin like the ShapedPlugin Pro builds has no published checksums, and it shows up as a warning. That's the gap the find check covers.

3. Try a Content Security Policy in report-only mode

A CSP tells the browser which hosts may serve scripts. Report-only mode logs the violations to the console and blocks nothing, which is the safe way to try one on a live store.

Nginx, for a store that takes cards through Stripe's hosted fields:

add_header Content-Security-Policy-Report-Only "script-src 'self' https://js.stripe.com; frame-src https://js.stripe.com" always; 

Open checkout with the console visible and place a test order. WooCommerce prints inline scripts on checkout, so expect reports for those too. Each one is a decision: allow it with a nonce or hash, or accept 'unsafe-inline' and rely on the host list.

Switch to the enforcing Content-Security-Policy header only when a full test order runs with no reports you don't understand.

4. Rate-limit checkout POSTs

Card testing bots submit many small orders to learn which stolen cards still work. The classic checkout posts to ?wc-ajax=checkout, and the block checkout posts to the Store API at /wp-json/wc/store/v1/checkout. Limit both, and only for POST:

# http {} block map "$request_method:$request_uri" $checkout_key { default ""; "~^POST:.*wc-ajax=checkout" $binary_remote_addr; "~^POST:/wp-json/wc/store(/v1)?/checkout" $binary_remote_addr; } limit_req_zone $checkout_key zone=checkout:10m rate=10r/m; # server {} block limit_req zone=checkout burst=5 nodelay; limit_req_status 429; 

Requests with an empty key are not counted, so the rest of the store is untouched. Ten attempts a minute is plenty for a person who mistyped a card number. It's very little for a script.

Shared IPs are the catch. An office or a mobile carrier can put many real buyers behind one address, so check the 429 count in your access log on the first sale day:

grep -c '" 429 ' /var/log/nginx/access.log 

Ask the payment provider about its own decline rules too. Most can block a card or IP after repeated declines without any server change.

The full checklist, with the admin account and backup steps, is on the canonical post.

What do you run on your stores during the sale week that isn't on this list?