Skip to content

WooCommerce Security Checklist: 20 Steps to Secure Your Store

Flat shield and checklist stack icon beside the title WooCommerce Security Checklist with 20 Steps

A WooCommerce security checklist is a set of steps that protects your store from hackers and automated attacks. It covers hosting, SSL, logins, payments and user access. Working through it closes the gaps attackers look for first.

Your store holds customer names, addresses and payment details. Bots scan WordPress sites around the clock and attack a public flaw within hours. By the time you notice a break-in, your payment processor may already be flagging your account.

We checked each of the 20 steps against the WordPress hardening guide and the WooCommerce docs in October 2026. For the steps that apply to any WordPress site, see our WordPress security checklist. To know whether WooCommerce is safe at all, read our test results.

Why WooCommerce Stores Are Prime Targets?

Why WooCommerce stores are targets for attackers

WooCommerce stores are targets because they run open-source code that anyone can study and they hold data worth stealing. Bots do not pick big brands. They scan thousands of sites for one unpatched plugin and attack whatever they find.

Your store holds customer names, addresses, email accounts and order details. That data has resale value. You do not need to be a major brand to get hit.

According to Patchstack’s State of WordPress Security in 2026, 11,334 new vulnerabilities were found in WordPress plugins, themes and core in 2025. That is a 42% increase on 2024. IBM’s Cost of a Data Breach Report 2026 puts the average global breach at $4.99 million.

Many breaches start with a forgotten admin account, an outdated plugin or a store that never enforced HTTPS. This WooCommerce security checklist walks you through all of them.

Section 1: Hosting and SSL Foundation

#1. Choose a WooCommerce-Optimized Host

Six host features that protect a WooCommerce store such as firewall and daily backups

Your hosting provider sets the floor for everything that follows. If it falls short, even strong security habits will not hold up for long.

Look for a server-level firewall, malware scanning and daily off-site backups. The host should also run a supported PHP version and keep each site isolated from its neighbors.

Ask how the host handles a hacked site before you sign up. Some isolate and clean the site for you, while others hand you the logs and leave the cleanup to you.

#2. Install SSL and Enforce HTTPS Across Your Entire Store

Three steps to move a WooCommerce store to HTTPS

SSL encrypts data between your site and your visitors for as long as your SSL certificate renewal happens on time. It’s essential at checkout. A common mistake is applying HTTPS only to the checkout page and leaving everything else unprotected.

WooCommerce’s security FAQ says every site that keeps user information should have an SSL certificate and run on HTTPS. Most hosts include a free certificate. After installation, force HTTPS across your entire domain. Set up a 301 redirect from HTTP to HTTPS so no unencrypted version of your site stays live. Then check every page, including the homepage and account pages, for the padlock in the browser bar.

Section 2: Keep Everything Updated

#3. Update WordPress Core and WooCommerce and PHP

PHP supported versions table with the PHP 8.2 security support end date marked
Source: PHP.net (October 2026)

Updates to WordPress core and PHP include security patches. Running old versions means running with known, public vulnerabilities.

When a patch is released, the release notes often describe what was fixed. That description tells attackers exactly what to look for on unpatched sites. The window between disclosure and active exploitation can be just a few hours.

Check your PHP version in your hosting dashboard. As of October 2026, PHP.net lists 8.2 to 8.5 as supported. PHP 8.2 gets security fixes only until 31 December 2026. PHP 8.1 or older gets no security patches at all. Plan the move to 8.3 or newer.

#4. Audit and Update All Plugins and Themes

WPScan WordPress plugin vulnerabilities page with the alphabetical plugin index
Source: WPScan (October 2026)

Per Patchstack’s 2026 report, 91% of the vulnerabilities found in 2025 were in plugins and 9% were in themes. Core WordPress had very few. Your plugin list is where the risk sits. You can check which plugin versions your site shows against known flaws with a free scanner.

If a plugin hasn’t been updated in over a year, treat it as a risk. You can check your plugins against WPScan’s vulnerability database to see if any known issues have been reported.

#5. Delete Every Plugin and Theme You’re Not Using

WordPress Plugins list with the Delete link under an inactive plugin

An inactive plugin still has files on your server. Those files can still be exploited. Deactivating a plugin doesn’t remove that risk. It just stops the plugin from running.

Go through your plugins and themes list. Delete old pre-installed themes and plugins you tested once and forgot. Remove tools from a campaign that ended months ago as well.

Section 3: Lock Down Your Login

Login pages are a main target on any WooCommerce store because one stolen password opens the whole dashboard. Bots try common usernames and leaked passwords all day. DevDiggers builds 26+ WooCommerce plugins, and two of them cover steps 8 and 10 below.

A CAPTCHA adds a bot check to login and checkout forms. Our roundup of the best WooCommerce CAPTCHA plugins compares free and paid options.

#6. Change the Default Admin Username and Login URL

WordPress Add User screen with a new username and the Administrator role selected

Create a new administrator account with a non-obvious username and give it full admin rights. Log in with the new account and then delete the original “admin” account.

You can also change your login URL away from /wp-admin and /wp-login.php. Both changes cut bot noise in your logs, but they do not stop a targeted attack. Do them after 2FA and login limits, which do the real work.

#7. Enforce Strong Passwords for All User Accounts

WordPress profile screen showing a very weak password and the confirm weak password checkbox

WordPress suggests a strong password, but a user can tick a box and keep a weak one. Every user with dashboard access needs a long, unique password that is not reused anywhere else. That includes editors, shop managers and any developer who had access.

Strong passwords are long and random. If your team is still choosing their own passwords, that’s a gap worth closing.

#8. Add Two-Factor Authentication to Your Store

Google Authenticator Configuration screen with the Enable WooCommerce Google Authenticator toggle

A strong password can still be compromised through phishing or a breach. Two-factor authentication adds a second layer that a stolen password alone can’t bypass.

Our WooCommerce Google Authenticator plugin adds 2FA with the Google Authenticator app, built by DevDiggers. Each user scans a QR code from their My Account page to enroll. After that, their login needs a six-digit code on both the store login form and wp-login.php.

#9. Limit Login Attempts and Block Repeated Failures

Limit Login Attempts and Block Repeated Failures

WordPress has no default limit on login attempts. An automated script can cycle through thousands of passwords without triggering any lockout. The free Limit Login Attempts Reloaded plugin adds that limit.

A plugin that limits attempts and blocks IP addresses after repeated failures stops this cold. Most dedicated WordPress security plugins include this feature.

#10. Add CAPTCHA to Login and Registration and Checkout Forms

Advanced CAPTCHA settings with Google reCAPTCHA Cloudflare Turnstile CAPTCHA and hCaptcha type options

Bots also hit registration forms, checkout pages and lost password forms. Unprotected forms invite spam accounts, fake orders and card-testing attacks.

Our WooCommerce Advanced CAPTCHA plugin adds CAPTCHA to your login, registration, lost password, checkout and review forms. It is built by DevDiggers and supports Google reCAPTCHA, Cloudflare Turnstile and hCaptcha. Staff IPs and chosen user roles can skip the check.

Section 4: Manage User Roles and Access

#11. Give Every User the Minimum Access They Need

WordPress Users list with the Role column showing shop manager editor and customer roles

WooCommerce and WordPress both support role-based access. A shop manager doesn’t need administrator rights. A copywriter updating product descriptions doesn’t need to install plugins. Give every user the lowest access level that lets them do their job.

An attacker with subscriber access cannot install malware. An attacker with administrator access can do almost anything, including creating backdoors and reading your full customer database.

#12. Audit and Remove Dormant Accounts

WP Activity Log plugin page on WordPress.org
Source: WordPress.org (October 2026)

Think about every person who has ever logged in to your WordPress dashboard. Accounts of former staff, freelancers and one-off developers that still exist are a live risk.

Remove accounts that no longer need access. If you’re unsure about an account, downgrade its permissions while you investigate. Use a plugin like WP Activity Log to quickly identify accounts that haven’t been active in months. It tracks logins, logouts and user activity in real time.

Section 5: Secure Your Checkout and Payment Flow

#13. Use a PCI-Compliant Payment Gateway

WooCommerce Payments settings with the PayPal Payments hosted gateway listed

PCI DSS (Payment Card Industry Data Security Standard) governs how card payment data is handled. WooCommerce’s security FAQ says a store using an integrated gateway, where cards are entered on your site, must be PCI compliant. An offsite gateway leaves far less on your side.

Hosted gateways such as Stripe and PayPal process card data on their own servers. Your server never touches the raw card number. For example, if you sell physical products and use a hosted gateway, your compliance obligation is much lighter because the sensitive data never passes through your infrastructure.

#14. Confirm Card Data Is Never Stored on Your Server

Comparison of where card data lives with and without payment tokens

Some older or poorly configured setups accidentally store card data without the store owner noticing. Check that your gateway handles all card processing on its end. Your WooCommerce database should never contain raw card numbers or CVV codes.

If your gateway supports tokenization, turn it on. Tokens let customers save payment methods without storing card data on your server. Repeat purchases stay quick for buyers, and the risk stays with the gateway.

#15. Review Your Checkout for Unnecessary Data Collection

Three steps to review checkout data collection

A secure WooCommerce checkout also depends on what data you collect and where it goes. Review your checkout form fields. Remove anything you do not need. Data you collect but don’t use is a liability.

Also, check your third-party integrations. Analytics tools, CRM systems, and affiliate trackers connected to checkout don’t need access to payment data. Most only need order totals. Tighten those integrations where you can.

Section 6: Harden Your WordPress Configuration

#16. Disable the WordPress File Editor

WordPress Theme File Editor screen with the menu item under Appearance

WordPress has a built-in editor for changing plugin and theme files from the dashboard. If an attacker gains admin access, this editor lets them inject malicious code without needing server access at all.

Disabling it takes one line in your "wp-config.php" file:

define( 'DISALLOW_FILE_EDIT', true );

Most WooCommerce stores have no reason to edit files through the dashboard. Use a local code editor and deploy via FTP or your host’s file manager instead. This takes 30 seconds. The WordPress hardening guide notes it will not stop an attacker from uploading files, but it closes one easy path.

#17. Change the Default WordPress Database Prefix

Brozzme DB Prefix and Tools Addons plugin page on WordPress.org with the Download button

Many published SQL injection attacks assume the default wp_ table prefix. The WordPress hardening guide says a custom prefix can block at least some of them. It is a small extra layer, and an unpatched plugin is still the real risk.

Set a random prefix such as store7x_ during a fresh install, where it costs nothing. On an existing site, take a full backup first and then use a plugin like Brozzme DB Prefix & Tools Addon to handle the change safely.

#18. Set Correct File Permissions

# For directories:
find /path/to/your/wordpress/install/ -type d -exec chmod 755 {} \;

# For files:
find /path/to/your/wordpress/install/ -type f -exec chmod 644 {} \;

# For wp-config.php:
chmod 440 wp-config.php

Wrong file permissions are an overlooked risk. If your files or directories are set too openly, anyone with partial server access can read or modify files.

The WordPress hardening guide uses 755 for directories and 644 for files. It sets 440 or 400 for wp-config.php so only you and the web server can read it. Check these through your hosting control panel. On managed WordPress hosting, your host may handle this automatically.

Section 7: Ongoing Monitoring and Recovery

Securing your store once isn’t enough. Threats change. New vulnerabilities appear in plugins you’ve used for years. Team members make mistakes. This section is where most checklists fall short. They cover setup and ignore everything that comes after.

#19. Set Up Daily Automated Backups Stored Off-Site

Set Up Daily Automated Backups Stored Off-Site

Back up your store daily at a minimum and store the copies off-site. That means a different server or cloud storage and not the same hosting account as your live site.

If your server is compromised and your backups are on the same server, you could lose both. A plugin like UpdraftPlus automates daily backups and sends them to Google Drive, Dropbox or Amazon S3. Restore a backup to a staging site every few months to prove it works.

#20. Install a Security Plugin for Malware Scanning and Firewall and Activity Logging

Wordfence Security plugin page on WordPress.org with the Download button and intro video

A web application firewall blocks malicious traffic before it hits your site. A malware scanner checks your files and database for signs of compromise. An activity log records logins, plugin changes, file edits and order changes.

A security plugin like Wordfence gives you the firewall and the malware scanner. Pair it with an activity log such as WP Activity Log from step 12. Run both on every WooCommerce store, whatever its size.

One more thing worth doing: write a basic breach response plan before you need one. Know who to contact first and how to take the site offline quickly. Write down how to restore from backup and what you must tell affected customers by law. A breach is the wrong moment to decide those things. If you think a breach has already happened, our WordPress hacked guide lists the signs to check and the recovery steps.

Conclusion

Working through this WooCommerce security checklist puts you ahead of most stores online. It starts with a solid host and current software. Then come protected logins, tight user access, safe payments and active monitoring.

If you are going to start somewhere, keep plugins updated, add 2FA to every admin account and protect your forms from bots. Those steps close the most common attack paths.

Our WooCommerce Google Authenticator plugin and WooCommerce Advanced CAPTCHA plugin handle two of those directly without developer skills. If you would rather get help with a security audit or with working through this checklist, our WooCommerce development services are available for exactly that.

Frequently Asked Questions (FAQs)

Q1. Is WooCommerce Secure by Default?

WooCommerce is maintained and patched by a dedicated team, and the core plugin is well built. The real risks come from third-party plugins, outdated themes, weak passwords and misconfigured hosting. WooCommerce gives you a solid base. How secure your store is depends heavily on what you build on top of it.

Q2. How Do I Know If My WooCommerce Store Has Been Hacked?

Watch for these signs: new admin accounts you didn’t create, your site redirecting visitors to another domain, Google flagging your site as dangerous, your host suspending your account, or customers reporting unexpected charges. An activity log and regular malware scans catch most of these early, before they affect customers or search rankings.

Q3. Do I Need a Security Plugin If My Host Already Provides Protection?

Yes, in most cases. Your host protects the server environment. A WordPress security plugin protects the application layer. Patchstack found 91% of 2025 WordPress vulnerabilities in plugins, and that layer is where they get exploited. These two layers work together. One doesn’t replace the other. Even strong managed hosts rarely provide WordPress-specific application-layer protection out of the box.

Q4. What Is PCI Compliance and Does It Apply to My WooCommerce Store?

PCI DSS applies to any business that accepts, sends or stores card payment data. That includes WooCommerce stores. The compliance level you need depends on your setup. Using a hosted gateway like Stripe means less sensitive data on your end and a lighter obligation. Processing cards directly on your server means a heavier burden. Check with your payment gateway provider for your specific requirements.

Q5. How Often Should I Work Through This WooCommerce Security Checklist?

A full review once a quarter works well for most stores. Checking for plugin updates and reviewing backup status should happen weekly. After any major WordPress or WooCommerce release, run a quick audit to confirm everything updated correctly. Security isn’t a one-time task. Treating this checklist as a regular habit is what keeps your store protected over time.

Rishi Yadav
Rishi Yadav

Rishi Yadav is a content writer at DevDiggers who covers WooCommerce store management, WordPress performance and security. He works through each topic in a test environment before writing about it. His guides focus on the steps and settings that matter and skip the ones that sound good on paper.

Leave a Reply

Your email address will not be published. Required fields are marked *