Security · Explainer
Is WordPress Secure? What the Vulnerability Data Shows
Short answer
WordPress core is secure when it is kept updated: Patchstack found only 6 flaws in WordPress core in 2025, all low priority, against 11,334 flaws across WordPress software and its plugins and themes. Most risk sits in plugins, which held 91% of those flaws, and in weak logins and late updates. A site that updates fast, limits plugins, and uses two-factor login is far harder to break into than one left alone.
Key takeaways
- WordPress core had only 6 flaws in 2025, all low priority, while plugins held 91% of the 11,334 flaws Patchstack counted.
- Nearly half of new flaws, 46%, had no developer fix when they were made public, so updates alone cannot close every gap.
- Heavily targeted flaws faced mass exploitation a median of 5 hours after disclosure, so patching speed matters.
- Sucuri's scanner found 1,176,701 infected sites in 2024, and 74.7% of them carried malware or redirects.
- A secure site runs current software and PHP 8.3 or newer, uses two-factor login, and keeps tested backups off the server.
- No public count gives a reliable total of hacked WordPress sites, because vendors measure different things.
Is WordPress secure?
Yes, WordPress core is secure when you keep it updated, but a WordPress site is only as safe as its plugins, themes, logins, and hosting.
WordPress.org says the project powers more than 43% of the web and has a security team of more than 50 trusted experts who review core code and ship fixes. See WordPress.org's security page.
W3Techs measured a smaller share. On 19 November 2026 it put WordPress on 38.5% of all websites and 57.4% of sites with a known CMS, according to W3Techs. The two counts use different methods, so quote each figure with its source and date.
That size cuts both ways. A flaw in a popular plugin can affect millions of sites at once, while a flaw in core gets found and fixed fast because so many people watch the code.
What does the vulnerability data actually show?
Patchstack counted 11,334 new WordPress flaws in 2025, up 42% on 2024, in its State of WordPress Security in 2026 report, updated 25 February 2026.
| Where the flaw was | Share of 2025 flaws | What it means |
|---|---|---|
| Plugins | 91% | Most flaws sit in add-ons, not in core |
| Themes | 9% | Themes hold a smaller share of flaws |
| WordPress core | 6 flaws, all low priority | Core itself had very few flaws |
Of those flaws, 1,966 were rated high severity, or 17%, and 4,124 were serious enough for Patchstack to write protection rules, or 36%. The 2024 total was 7,966 flaws.
A flaw count is not a hacked-site count. It records flaws that researchers found and reported, not sites that were broken into. Most of the 11,334 flaws were low impact or needed a logged-in attacker, so read the split by severity before judging the risk.
Where do most WordPress security problems come from?
Most problems come from plugins and themes, weak or stolen logins, and old software, not from WordPress core.
Patchstack found that broken access control was the most exploited flaw type in 2025. That means code failed to check who was allowed to do something, so a visitor could reach an action meant for an admin.
Old software adds risk. WordPress.org says only the latest major release is officially supported, and fixes for older branches arrive only as a courtesy. Check each plugin with our guide to finding abandoned WordPress plugins before you trust it with your site.
Nulled copies are a separate trap. They are paid plugins or themes offered free by unknown third parties, and they can hide added code while receiving no updates. Download WordPress only from WordPress.org, and get plugins and themes from the official directory or the author's own site.
How fast do attackers act after a flaw is disclosed?
For heavily targeted flaws, mass exploitation started a median of 5 hours after disclosure, according to Patchstack's State of WordPress Security in 2026 report.
About half of high-impact flaws were exploited within 24 hours of disclosure. That window is why a weekly update routine is not enough on its own for a busy site.
Worse, 46% of flaws had no developer fix when they were made public. In that gap, a firewall is the main defence: it can block attack patterns while you wait for a patch.
Our guide to Cloudflare WAF rules for WordPress shows how an edge firewall filters requests before they reach your site.
Patchstack also ran a large pentest of popular hosts in 2025 and found that common hosting defences blocked only 26% of vulnerability attacks. A host firewall helps, but it does not replace updates and login checks.
How often do WordPress sites get hacked, and what happens then?
No public count gives a reliable total of hacked WordPress sites, but Sucuri's scanner found 1,176,701 infected sites in 2024.
Sucuri ran 70.8 million scans in 2024 for its SiteCheck Malware Trends Report 2024. Malware and redirects made up 74.7% of infections. The Balada Injector campaign appeared 149,351 times, and Sign1 appeared 96,084 times.
Once inside, attackers often add spam pages, redirect visitors to scam sites, or plant phishing pages. Google lists the result in Search Console under “Security issues”, in three groups: hacked content, malware, and social engineering.
Affected pages can show a warning label in search results or a full warning page in the browser, as Google explains in its Security issues report help page.
Counts from different vendors are not directly comparable. Sucuri counts infected sites its scanner saw, Patchstack counts flaws researchers reported, and Wordfence counts attacks its firewall blocked. Each measures a different thing.
What makes a WordPress site secure in practice?
A secure site runs current core, plugins, themes, and PHP, uses strong logins with two-factor login, and keeps tested backups off the server.
- Update everything, then turn on auto-updates. Minor core updates install on their own, and plugin and theme auto-updates have been built in since WordPress 5.5. Delete plugins and themes you no longer use.
- Run supported PHP. WordPress.org's requirements page recommends PHP 8.3 or newer, MariaDB 10.11 or newer or MySQL 8.4 or newer, and HTTPS support. It warns that PHP 7.4 and MySQL 5.5.5 still work but are past end of life and may expose a site to flaws.
- Lock down logins. Use a long, unique password for each account, give each person the lowest role that fits the job, and turn on two-factor login for every admin and editor. WordPress core does not ship two-factor login, so you need a plugin for it.
- Use HTTPS on every page. A certificate encrypts logins and checkout pages. See Let's Encrypt vs paid SSL to pick a certificate type.
- Harden files. The Hardening WordPress handbook lists 755 for directories and 644 for files, with wp-config.php at 400 or 440. It also covers DISALLOW_FILE_EDIT, which turns off the dashboard file editor.
- Keep tested backups off the server. A backup on the same server can be wiped or locked in the same attack. See how to back up WordPress for a full routine.
How do you check if your WordPress site is secure?
Open “Tools → Site Health” in your dashboard, check your WordPress version and PHP version, and fix every item it flags as a security issue.
Then work through this short check:
- Open “Dashboard → Updates” and install every pending update for core, plugins, and themes.
- Open “Plugins → Installed Plugins” and delete anything you do not use or that has no update in over a year.
- Check “Users → All Users” for accounts you do not know, and remove any admin account you cannot name.
- Open Search Console and look at “Security issues” for hacked content, malware, or social engineering flags.
- Run an outside scan, such as Sucuri SiteCheck, and compare what it finds with your own file list.
Repeat the check after every major update. A site that was clean last month can pick up a new flaw when a plugin ships a bad release.
Is WordPress more secure than a custom-coded site?
Neither is safe by default. WordPress gets faster public fixes, while custom code gets less review and hides its flaws longer.
WordPress core is open source, so many reviewers read the code and fixes ship to millions of sites at once, often through automatic updates. A custom site has a smaller attack surface in one sense: attackers cannot reuse a known plugin flaw against it.
But size cuts the other way too. Attackers scan the web for sites running a named plugin version with a known flaw, so a popular plugin flaw can be hit at scale within hours.
A custom site is less likely to face that kind of mass scan, yet a single flaw in its own code can sit unnoticed for years.
Do you need a security plugin to keep WordPress safe?
No, but one plugin that adds a firewall, a scanner, and login protection helps if you set it up and keep it updated.
A security plugin is one layer, not a fix on its own. It can block known attack patterns, warn you when a file changes, and limit login attempts. It cannot fix weak passwords, replace backups, or patch a plugin whose author has stopped work.
Pick one plugin and learn its settings. Our guide to setting up the Wordfence firewall walks through the main options. Running two firewalls or three scanners at once adds conflicts and slows the site without adding safety.
What mistakes should you avoid?
The costliest mistakes are waiting to update, installing nulled code, and reusing passwords.
- Waiting weeks to install updates, when heavily targeted flaws are hit within hours of disclosure.
- Installing nulled plugins or themes. See are nulled WordPress plugins safe for why free copies of paid code are a risk.
- Reusing one password across your hosting, email, and WordPress admin accounts.
- Giving every helper an admin account instead of the lowest role that fits the job.
- Keeping your only backup on the same server as the site it protects.
Frequently asked questions
Is WordPress safe for a business website?
Yes, if you maintain it. A business site on current WordPress core, with few well-kept plugins, two-factor login, HTTPS, and tested backups, is a normal and defensible choice. The risk grows when updates slip, plugins pile up, or several people share one admin login. Put one person in charge of updates and checks, and review the plugin list every few months.
Is WordPress safe for an online store?
Yes, with the same care plus payment safety. Keep WooCommerce and its payment extensions updated, use HTTPS on every page, and limit who can see orders and customer data. A store is a bigger target because it holds customer and payment details, so test your backups and check your login list more often than a plain blog would need.
Can a WordPress site be hacked even with a security plugin?
Yes. A plugin blocks known attacks and warns about changed files, but it cannot fix a weak password, patch a plugin with no fix, or clean a site that was already broken into. In 2025, 46% of new flaws had no developer fix when they were made public, so a firewall and fast updates matter as much as the plugin itself.
How do I know if my WordPress site has been hacked?
Look for pages you did not write, redirects to strange sites, a sudden drop in search traffic, or a warning in Search Console under Security issues. Check the Users screen for unknown admin accounts and the Plugins screen for items you did not install. If you find anything odd, change every password and restore from a known-clean backup.
Does WordPress update itself when a security flaw is found?
Minor core security releases install on their own by default. Major core releases, plugins, and themes update on their own only if you turn auto-updates on for them. Open the Updates screen after a security release is announced and install anything still waiting, rather than assuming it is already done.
Should I delete plugins I no longer use?
Yes, delete them rather than leaving them switched off. A switched-off plugin still sits on the server, and an old one can still carry a flaw that attackers scan for. Keep only the plugins your site needs, and check the rest for a recent update and an active author before you keep them.
Sources
- State of WordPress Security in 2026 Patchstack
- SiteCheck Malware Trends Report 2024 Sucuri
- Security WordPress.org
- Requirements WordPress.org
- Hardening WordPress WordPress Developer Resources
- Usage Statistics and Market Share of WordPress, November 2026 W3Techs
- Security issues report Google Search Console Help
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
