Skip to content

Web design, software and technical support

Log in +90 539 219 79 78 WhatsApp
WordPress

A practical WordPress security checklist

Most WordPress sites are not harmed by sophisticated attacks but by outdated plugins, weak passwords and missing backups. This is a practical security checklist you can apply on a regular schedule.

Boran KaradenizKarınca Bilişim Last updated: 8 min

Summarise this article with an AI tool

The tool opens in a new tab with a summary prompt that includes this article’s address.

WordPress security comes from keeping core, themes and plugins updated, giving users only the permissions they need, using two-factor authentication on admin accounts, keeping tested backups off the server, removing unused plugins, setting correct file permissions, limiting login attempts and monitoring changes to the site.

Why are WordPress sites attacked?

Most WordPress sites are attacked by automated scans rather than targeted attacks. Tools search thousands of sites at once for plugin and theme versions with known vulnerabilities, weak passwords and exposed admin endpoints. "Our site is too small to matter" is not a safe assumption.

WordPress core receives regular security updates. Most of the risk comes from plugins that are not updated or have been abandoned, themes downloaded from unlicensed sources and shared admin accounts. This checklist is built to reduce those risks. Most items need no technical knowledge; for server settings you may need help from your host or developer. Treat it as a recurring routine, not a one-off task.

How should updates be managed?

Updates should be regular and controlled: keep core, themes and plugins current, take a backup before each update and check critical features afterwards. Delaying security updates leaves a window in which a vulnerability is public but still open on your site.

  • Allow automatic updates for minor WordPress security releases.
  • Update plugins and themes on a set schedule, after a backup.
  • Test major version updates on a staging site where possible.
  • Keep PHP on a supported version; old PHP versions no longer receive security fixes.
  • After updating, check forms, checkout and membership flows.

Our article What to check before a WordPress update covers pre-update checks in detail.

How should user accounts and roles be set up?

Each person should have only the permissions they need to do their job. WordPress provides the Administrator, Editor, Author, Contributor and Subscriber roles for exactly this purpose.

  • Give everyone their own account; never share an administrator login.
  • Give content staff the Editor or Author role, not Administrator.
  • Remove access for people who leave and agencies whose work has ended.
  • Avoid predictable usernames such as "admin".
  • Review administrator accounts regularly; an admin you do not recognise is a serious warning sign.

Is two-factor authentication necessary?

Yes, for administrator and editor accounts. Even if a password leaks, the account cannot be opened without the second factor. Authenticator apps are generally considered safer than SMS codes. Strong, unique passwords stored in a password manager are equally basic.

How should backups be handled?

Backups should cover both database and files, be stored off the server and be restored in a test at least occasionally. A backup kept only on the same server is useless if that server is lost or compromised.

CheckWhy it matters
Are the database and files backed up together?One without the other will not bring the site back.
Are backups stored off the server?A server problem can affect backups too.
Does frequency match how often content changes?For a busy store, even daily backups may not be enough.
Are several past copies kept?An unnoticed infection may already be in the latest backup.
When was a restore last tested?An untested backup is one you cannot rely on.

Why does plugin and theme hygiene matter?

Every plugin adds new code and a new attack surface. A deactivated plugin still leaves its files on the server.

  • Delete unused plugins and themes rather than just deactivating them.
  • Install plugins only from the WordPress.org directory or the developer's official source; "free" copies of paid plugins can contain malicious code.
  • Replace plugins that have not been updated for a long time.
  • Avoid several plugins that do the same job.
  • One maintainable custom plugin can be safer than many plugins stitched together.

What should be checked on the server?

Server and file settings aim to limit what an attacker can do even after finding a weakness:

  1. Serve the site over HTTPS only and redirect HTTP to HTTPS.
  2. Restrict file permissions; 755 for folders and 644 for files is usually enough, and wp-config.php can be tighter.
  3. Disable theme and plugin file editing in the dashboard with DISALLOW_FILE_EDIT.
  4. Block PHP execution in the uploads folder.
  5. Give the database user only the privileges it needs.
  6. Make sure debug mode is off on the live site.
  7. Connect with SFTP or SSH keys instead of plain FTP.

Do you need a web application firewall?

A web application firewall (WAF) is a valuable extra layer because it blocks known attack patterns before they reach the site. It can come from your host, a CDN or a plugin. A WAF does not replace updates; against an unpatched vulnerability it offers only temporary protection.

How should the login page be protected?

Protect the login page with attempt limits and an extra verification step. Temporary lockouts after repeated failures, two-factor authentication and, where practical, admin access restricted to known IP addresses all help. Disabling unused endpoints such as XML-RPC also reduces the surface for password guessing.

What extra steps apply to WooCommerce stores?

Stores hold customer, order and payment information, so the scope widens. Payment details should be handled on the payment provider's page or secure field, and card data should never be stored in the site's database.

  • Give the Shop Manager role only to people who manage orders and products.
  • Keep payment plugins and provider credentials up to date.
  • Enforce strong passwords for customer accounts and consider bot protection on registration.
  • Do not leave export files with order or customer data on the server.
  • Match backup frequency to order volume; lost order data is the hardest loss to recover.
  • Align retention and deletion of personal data with your privacy notices.

Why are monitoring and logs necessary?

Monitoring and logs show when a problem started and what changed. An unnoticed infection can publish spam or redirect visitors for weeks.

  • Use uptime monitoring to catch outages.
  • Use file change monitoring to spot unexpected changes in core files.
  • Log administrator logins and user changes.
  • Check the Security issues report in Search Console regularly.

What should you do after an attack?

First stop the damage spreading, then return to a clean state and close the cause. Hasty, random deletions make the cause harder to find.

  1. Take a copy of the site in its current state for investigation.
  2. Change all admin, hosting, FTP and database passwords.
  3. Identify unknown user accounts and files.
  4. Restore from a backup you know is clean, or reinstall core, themes and plugins from official sources.
  5. Find and update or remove the plugin or setting that let the attacker in.
  6. If Search Console shows a security warning, request a review after the clean-up.
  7. If visitor or customer data was affected, assess your legal notification duties under the data protection law that applies to you.

Who should run these checks, and how often?

Some checks belong with every update, some monthly and some a few times a year, and each needs a named owner. Security tasks with no owner are tasks that never happen. A simple rhythm works: updates and backup checks weekly, a user and plugin review monthly, a restore test and password rotation a few times a year.

Karınca Bilişim ties updates, backups and monitoring to a regular plan as part of website maintenance and security. If your site has a problem now, reach us through WordPress support or the contact form.

Frequently asked questions

Is a security plugin enough?

Not on its own. Security plugins add useful layers such as login protection, scanning and a firewall, but they cannot make up for outdated plugins, weak passwords or missing backups. Use a plugin as one part of the checklist.

Does changing the login URL improve security?

It can cut automated login traffic, but it is not real protection. Strong passwords, two-factor authentication and attempt limits are what protect the login. A custom URL belongs alongside these measures, not instead of them.

How often should backups run?

It depends on how quickly the site's data changes. A rarely updated company site may be fine with weekly backups, while a store taking orders every day needs them more often. Decide the longest period of data you could accept losing.

What is the risk of unlicensed themes or plugins?

Unlicensed copies receive no updates and often contain malicious code that can add hidden admin accounts or redirect visitors to other sites.

All articles
Call nowWhatsApp