WordPress Security in 2026: Essential Hosting, Backup and Plugin Protection

Where WordPress sites are exposed this year, what good hosting should handle for you, and the backup and plugin habits that close the gaps.

Illustration of a shield protecting a website
On this page
  1. What's changed for WordPress security in 2026
  2. Who protects what: you, your host and your plugins
  3. What your hosting should handle
  4. A backup plan that survives a bad day
  5. Plugin protection: choose, update and remove
  6. Lock down logins and access
  7. Keep WordPress core and PHP current
  8. If your site is hacked: the first hour
  9. Your 2026 WordPress security checklist
  10. Frequently asked questions
  11. Sources

WordPress core itself had very few security problems in 2025. The risk sits in the plugins and themes added to it. Patchstack's State of WordPress Security in 2026 report counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025, 42% more than the year before. It found 91% in plugins, 9% in themes and just six, all low priority, in WordPress core. Nearly half had no fix from the developer when they were made public.

That changes what "keeping WordPress secure" means in 2026. Updating promptly still matters, but it isn't enough on its own. You also need hosting that does its share, backups you can actually restore, and fewer, better-chosen plugins.

What's changed for WordPress security in 2026

  • Attacks start fast. Patchstack reports a weighted median of five hours from disclosure to the first exploit attempt for heavily exploited vulnerabilities, and that about half of high-impact vulnerabilities were exploited within 24 hours.
  • Many fixes arrive late. 46% of vulnerabilities didn't receive a developer fix in time for public disclosure, so an update may not exist yet when attacks begin.
  • Generic defenses miss a lot. In Patchstack's tests against hosting setups, traditional defenses blocked 12% of attacks on known-exploited WordPress vulnerabilities, and 26% across a wider set of vulnerabilities. It says results varied widely between hosts.
  • Premium isn't automatically safer. Patchstack found three times as many known exploited vulnerabilities in premium components as in free ones.
  • Core updates still matter. WordPress 7.1.4, released on October 28, 2026, is a security release, and WordPress.org recommends updating immediately.
  • The end of the year is busy. Monarx, Patchstack's partner on the report, saw malicious uploads nearly triple in November and December.

Who protects what: you, your host and your plugins

Security comes in layers, and different people are responsible for each one. Most problems happen when everyone assumes someone else is handling a layer.

Stacked diagram of five WordPress security layers: hosting and firewall, HTTPS, updates, logins and roles, and backups and monitoring.
Each layer covers gaps the others can miss.
Typical security responsibilities by hosting type
LayerShared hostingManaged WordPress hostingUnmanaged VPS
Server and operating system patchesHostHostYou
Account isolation and network firewallHostHostYou, within the provider's network
Web application firewall and malware scanningVaries by planUsually hostYou
BackupsHost, plus your own copiesHost, plus your own copiesYou, unless you add a backup service
WordPress core updatesAutomatic for minor releases; you for major onesOften hostYou
Plugin and theme updatesYouVaries by host and planYou
Choosing plugins, logins and user rolesYouYouYou

This is a general pattern, not a promise from any provider, so check your own plan. If you run a VPS, our guide to what managing a VPS involves covers the extra work.

What your hosting should handle

A host can't fix a vulnerable plugin for you, but it can make attacks harder and recovery quicker. Look for these on the plan page, and ask about anything missing:

  • Account or site isolation, so a compromised site next door can't reach yours
  • PHP running under your own account user. WordPress.org's requirements page says this is more secure than a shared server user
  • A web application firewall that filters malicious requests before they reach WordPress
  • Malware scanning and clean-up, and a clear answer on what happens if your site is infected
  • Automatic daily backups stored off the server, with restores you can run yourself
  • Current PHP versions you can choose, with older versions retired on time
  • Free SSL that renews automatically, and SFTP or SSH instead of plain FTP
  • Two-factor sign-in for the hosting account, which controls everything else
  • Staging, so you can test updates before they reach the live site

What DreamHost and Hosting.com list

These are the security and backup features each provider publishes. They tell you what's included, not how effective it is.

Published security and backup features, from official pages and WebPrash's reviews
PlanBackupsFirewall and malwareOther
DreamHost Web HostingDaily automated, one-click restore. DreamHost generally keeps about two weeks of file backups but doesn't guarantee themOne DreamShield malware scan per site per month on Growth and Scale; not on LaunchFree SSL; no staging on these plans
DreamPressDaily, stored offsite on Amazon S3, kept 14 or 30 days by plan; on-demand and locked backupsDreamHost's WooCommerce page mentions a WAF; the DreamPress plan page doesn't detail it, so confirm1-click staging; SSL
Hosting.com sharedDaily, kept 30 days off the server, with restores of sites, files, databases and mailboxesModSecurity WAF, Monarx malware detection and removal, DDoS filtering, brute-force protectionPer-site container isolation, two-factor authentication; staging on Pro and Max
Hosting.com Managed WordPressDaily, kept 14 daysWeb application firewall, malware monitoring and clean-upAutomatic updates; staging on every plan

Details come from our DreamHost, DreamPress, Hosting.com and Hosting.com Managed WordPress reviews, which link to each provider's source pages. WP Engine is another option, listing firewalls, malware scans and backups kept for 30 to 60 days, though its managed WAF is a paid add-on on the Essential plan.

Our view: if you'd rather not manage security tools yourself, a plan that lists a WAF, malware clean-up and off-server backups saves real work. Of the plans in this table, Hosting.com's shared plans list the most security features.

View Hosting.com Shared Hosting Plans (opens Hosting.com Shared Hosting in a new tab)

View DreamPress Plans (opens DreamHost: DreamPress – High-Performance WordPress in a new tab)

A backup plan that survives a bad day

Backups are what let you recover when every other layer fails. WordPress's backup guidance says to back up both the database and the files, to back up regularly and before updates, to keep copies in more than one place, and to test that you can restore them.

Three panels showing where to keep website backups: with your host, in cloud storage and on your own computer.
Keep copies in more than one place, so one failure can't take them all.

Host backups are convenient, but they aren't the whole plan:

  • Retention is limited. A malware infection can sit unnoticed for weeks. If your host keeps 14 days of backups, the clean ones may already be gone. Keep some older copies yourself.
  • They live with your account. If the account is suspended, compromised or closed, its backups may go with it.
  • A restore replaces the live site. Our DreamPress review notes this, and it's true of most full restores. On a store, anything since the backup, including orders, is lost unless you export it first.

A sensible routine for most small business sites:

  1. Keep the host's daily backups switched on, and note how many days they're kept.
  2. Add your own automatic backups to separate cloud storage, at least weekly, or daily for busy or ecommerce sites.
  3. Take an on-demand backup before every update, plugin install or design change.
  4. Keep a monthly copy for several months, so you can go back further than an infection.
  5. Test a restore on a staging site a few times a year.

Plugin protection: choose, update and remove

With 91% of new vulnerabilities in plugins, how you handle plugins is the biggest factor you control.

Before you install

  • Ask whether you need it at all. Every plugin is code that needs updating.
  • Check when it was last updated and whether it's tested with your WordPress version.
  • Look at how the developer handles support questions and security reports.
  • Download only from WordPress.org or the developer's own site, never from "nulled" copies.
  • Don't assume a premium plugin is safer because you paid for it.

Once it's installed

  • Turn on automatic updates for well-maintained plugins you trust. WordPress has supported this for plugins and themes since version 5.5.
  • Get vulnerability alerts. Services such as Patchstack, Wordfence and WPScan publish vulnerability databases and alerts for the plugins you use. We haven't compared them, so treat these as examples rather than recommendations.
  • Consider virtual patching for business-critical sites. It's a firewall rule that blocks a specific vulnerability before a plugin update exists, which helps in the gap Patchstack describes.
  • Delete what you don't use. Deactivated plugins and themes can still contain vulnerable code.

Our guide to the best WordPress tools for beginners includes a plan for avoiding plugin overload.

Lock down logins and access

Stolen or guessed passwords remain an easy way in, and they bypass every other layer. In short:

  • Use a unique, generated password for every account, and two-step authentication for every administrator. WordPress's two-step authentication guidance recommends app-based codes over SMS.
  • Give each person the lowest role they need, and remove accounts for people who've left.
  • Review application passwords under each user's profile, and revoke any you don't recognize.
  • Protect the accounts around WordPress too: hosting, domain registrar and email.

Our WordPress security checklist covers these steps, plus switching off the dashboard file editor, in more detail.

Keep WordPress core and PHP current

WordPress installs minor and security releases automatically by default, but check that it has. As of November 14, 2026, you should be on 7.1.4. WordPress 7.2 is in beta and scheduled for December 8, 2026. WordPress.org says not to run betas on production sites, so test it on staging only.

PHP matters too. PHP 8.2 stops receiving security fixes on December 31, 2026, according to the WordPress Hosting Handbook. If you're still on it, plan a move to PHP 8.3 or, better, 8.4. Our guide to WordPress 7.1 hosting requirements explains how to check and upgrade.

Looking ahead, the 7.2 beta includes a Secrets API, a standard way for plugins to store credentials such as API keys with encryption at rest. It isn't in a stable release yet.

If your site is hacked: the first hour

  1. Don't delete everything. Take a copy of the site as it is, so you or a specialist can find how the attacker got in.
  2. Contact your host. Many can spot the problem in server logs, and plans that include malware clean-up may handle it for you.
  3. Change every password: WordPress users, hosting, database, SFTP and the email account linked to the site.
  4. Restore a clean backup or have the site cleaned. On a store, export recent orders first.
  5. Close the gap. Update everything, remove unknown users and plugins, and find the vulnerable component, or you'll be reinfected.

Your 2026 WordPress security checklist

  • WordPress is on 7.1.4, and PHP is 8.3 or newer
  • Every plugin and theme is needed, maintained and up to date
  • You get alerts when a plugin you use has a known vulnerability
  • A web application firewall is in place at the host or through one security plugin
  • Daily backups are stored off the server, with older copies kept and a tested restore
  • Administrators use two-step authentication and unique passwords
  • Your hosting account, registrar and email use two-step sign-in too
  • Updates are tested on staging when they're major or the site is business-critical
  • You know who to contact, and what your plan covers, if the site is hacked

Frequently asked questions

Is WordPress secure in 2026?

WordPress core is actively maintained and had few security issues in 2025. Most risk comes from plugins, themes, weak passwords and outdated software, which you can control.

Do I need a security plugin if my host has a firewall?

Not necessarily. If your host provides a WordPress-aware firewall, malware scanning and backups, a plugin may add little. If it doesn't, one reputable security plugin can fill the gap. Avoid running several at once.

How often should I back up WordPress?

WordPress's guidance suggests weekly for smaller sites and daily for busy ones, plus before every update. Keep copies in more than one place, and keep some older than your host's retention period.

Are premium plugins safer than free ones?

Not automatically. Patchstack's 2026 report found three times as many known exploited vulnerabilities in premium components as in free ones. Judge any plugin by its maintenance record and how its developer handles security reports.

Does managed WordPress hosting make my site secure?

It covers more layers, often including updates, a firewall and malware clean-up, but you still choose the plugins, manage user accounts and keep your own backups.

What is virtual patching?

It's a firewall rule that blocks attempts to exploit a specific known vulnerability, so a site stays protected until the plugin developer releases a fix.

Sources

Facts last checked: November 14, 2026. Security features and plan details change, so confirm them with your host. This guide isn't a substitute for professional incident response.