Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Explainer

The Most Common WordPress Vulnerability Types

Short answer

The most common WordPress vulnerabilities are broken access control, injection flaws such as SQL injection and cross-site scripting, cross-site request forgery, outdated plugins and themes, and weak logins. Patchstack counted 11,334 new WordPress vulnerabilities in 2025, and 91% of them were in plugins. Keeping everything updated, using strong logins, and checking plugins against a vulnerability database cut most of this risk.

Key takeaways

  • Patchstack counted 11,334 new WordPress vulnerabilities in 2025, and 91% were in plugins, 9% in themes, and only 6 in core.
  • Broken access control was the most exploited vulnerability type in 2025, and it lets users act outside their intended permissions.
  • Injection flaws let untrusted input reach an interpreter, and OWASP links more than 30,000 cross-site scripting CVEs to this category.
  • 46% of new vulnerabilities had no developer fix when they were disclosed, so updates alone cannot close every gap.
  • WPScan catalogs 94,710 WordPress core, plugin, and theme vulnerabilities as of November 2026, and you can search it for free.
  • WordPress powers more than 43% of the web, so a flaw in one popular plugin can put a large number of sites at risk.

What are the most common WordPress vulnerabilities?

The most common types are broken access control, injection flaws, cross-site request forgery, outdated plugins and themes, and weak logins.

A vulnerability is a flaw that lets an attacker do something the developer never intended, such as read private data, change content, or take over a site. Most WordPress flaws sit in plugins and themes, not in WordPress core itself.

Patchstack counted 11,334 new WordPress vulnerabilities in 2025, a 42% rise on 2024, in its State of WordPress Security in 2026 report (checked November 2026). Of those, 91% were in plugins and 9% in themes, while only 6 were in WordPress core, all low priority.

What is broken access control in WordPress?

Broken access control means a user can do something outside their intended permissions, such as view another user's data or use an admin-only function.

Access control is the set of checks that decide who can do what. When a check is missing, a logged-in subscriber may reach an admin page, or a visitor may call an API action that should need a login.

OWASP puts broken access control at number 1 in its OWASP Top 10:2025 list (checked November 2026). Its A01 page says 100% of the applications tested had some form of broken access control, across 40 mapped weakness types and 32,654 related CVEs.

Patchstack also names broken access control as the most exploited vulnerability type in 2025, in the same report linked above. It is hard to block with a basic firewall because the requests look like normal logged-in traffic with no obvious injection pattern.

Common forms include:

  • A low-privilege user gaining admin rights, known as privilege escalation.
  • Viewing or editing someone else's account by changing an ID in a URL.
  • An API endpoint that accepts POST, PUT, or DELETE requests without checking who sent them.
  • Guessing admin URLs, known as force browsing, without logging in.

Your job is to keep those plugins updated, give each user the lowest role that fits their work, and remove accounts you no longer need.

What is SQL injection and cross-site scripting?

Injection happens when untrusted input reaches an interpreter, such as a database or a browser, and gets run as code instead of treated as plain data.

SQL injection targets the database. A flaw in a search box, form, or filter can let crafted input change a database query, so it returns, changes, or deletes data it should not touch.

Cross-site scripting, or XSS, targets the browser. A flaw lets an attacker store or reflect a script that runs in a visitor's or admin's browser, where it can steal a session or change what the page shows.

OWASP lists injection at number 5 in its OWASP Top 10:2025 list, and its A05 page links more than 30,000 cross-site scripting CVEs and more than 14,000 SQL injection CVEs to this category (checked November 2026). The page also notes that 100% of applications tested were checked for some form of injection.

FlawTargetWhat it can do
SQL injectionDatabaseRead, change, or delete data it should not touch
Stored cross-site scriptingVisitor or admin browserRun a script in someone else's browser session
Reflected cross-site scriptingVisitor browserRun a script from a crafted link
Command injectionServerRun operating system commands on the server

You cannot fix these flaws yourself when they sit in a plugin. Update the plugin, delete plugins you do not use, and use a firewall that filters known attack patterns before they reach WordPress.

What is cross-site request forgery (CSRF)?

Cross-site request forgery tricks a logged-in user's browser into sending a request the user did not intend, such as changing a setting or deleting content.

The attack works because the browser sends the user's login cookie with the request. The site then treats the request as genuine, even though it came from a page the user visited elsewhere.

OWASP groups cross-site request forgery under broken access control in its OWASP Top 10:2025 list (checked November 2026). WordPress core defends against it with nonces, which are one-time tokens added to forms and links that change state.

A nonce is a single-use value that proves a request came from a real page on your site. A plugin that skips this check on an action, such as saving settings or deleting a post, leaves that action open to forgery.

If a vulnerability database flags a CSRF flaw in a plugin you use, update it at once or replace it.

Why are outdated plugins and themes the biggest risk?

Outdated plugins and themes are the biggest risk because most new WordPress flaws are found in them, and attackers scan for old versions within hours of disclosure.

Patchstack counted 11,334 new vulnerabilities in 2025, and 91% were in plugins, as noted above. Only 6 were in WordPress core, so updating core alone does not cover the risk.

The speed matters as much as the count. Patchstack found that about half of high-impact vulnerabilities were exploited within 24 hours, and the weighted median time to first mass exploitation for heavily targeted flaws was 5 hours (checked November 2026).

Worse, 46% of new vulnerabilities had no developer fix when they were disclosed, according to the same Patchstack report. That means an update may not exist yet, and a firewall rule or removing the plugin may be the only cover until a fix ships.

To cut this risk, follow the advice in our guide on how to find abandoned WordPress plugins. Check each plugin's last update date, replace anything unmaintained for over a year, and delete plugins and themes you do not use.

What is a supply chain vulnerability in WordPress?

A supply chain vulnerability is a flaw in code your site depends on, such as a plugin, theme, or library, that reaches your site through a normal update or install.

OWASP added software supply chain failures as a new category at number 3 in its OWASP Top 10:2025 list (checked November 2026). For WordPress, the supply chain is mostly plugins and themes, plus the libraries they bundle.

Patchstack found that premium components carry real risk too. In its 2026 report, 1,983 valid vulnerability reports covered premium or freemium components, and 76% of the flaws found in premium components were exploitable in real attacks (checked November 2026).

Nulled plugins are a sharp form of this risk. They are cracked copies of paid plugins, often with added backdoors, and they receive no updates. Read our guide on whether nulled WordPress plugins are safe before you install anything from an unofficial source.

How do weak logins and brute-force attacks work?

A brute-force attack guesses usernames and passwords over and over, often with automated bots, until one combination works.

WordPress has no built-in limit on login attempts, so a bot can try thousands of combinations against wp-login.php. Weak passwords, reused passwords, and the default username “admin” make that job far easier.

The WordPress hardening guide lists brute-force password guessing as one of the two most common attacks on a site, next to crafted requests that target known flaws. See its Hardening WordPress handbook (checked November 2026).

The same guide says a hacker who gains an admin account can install scripts that can compromise the whole server.

Defend logins with these steps:

  • Use a long, unique password for every admin account, stored in a password manager.
  • Turn on two-factor authentication for every administrator and editor.
  • Use a username other than “admin” and remove accounts you no longer need.
  • Limit login attempts with a security plugin or a firewall rule.

What is security misconfiguration on a WordPress site?

Security misconfiguration means a setting, file permission, or server option is left open in a way that helps an attacker, such as directory listing or debug output on a live site.

OWASP lists security misconfiguration at number 2 in its OWASP Top 10:2025 list (checked November 2026). On WordPress, common examples include leaving WP_DEBUG on in production, exposing backup files, and leaving directory listing enabled.

File permissions are a simple place to start. The WordPress hardening guide recommends directories at 755 and files at 644, and wp-config.php at 400 or 440, in its Hardening WordPress handbook (checked November 2026).

The same guide recommends adding define( 'DISALLOW_FILE_EDIT', true ); to wp-config.php. That line turns off the dashboard file editor for every user, so a stolen admin login cannot be used to edit theme or plugin code from inside the dashboard.

Other useful checks include forcing HTTPS for admin pages, deleting install files and old backups from the web root, and keeping only the themes and plugins you use. A firewall can add a further layer; see our guide to Cloudflare WAF rules for WordPress for one way to set that up.

How can you check your site for known vulnerabilities?

Check your site by listing every plugin and theme version, then searching each one in a vulnerability database such as WPScan.

WPScan catalogs 94,710 WordPress core, plugin, and theme vulnerabilities as of November 2026, according to its homepage (checked November 2026). Each entry lists the affected versions, the fixed version, and a severity score.

Follow these steps once a month, and after any security news about a plugin you use:

  1. Open Dashboard, then Plugins, and note the version of each active plugin.
  2. Do the same for Appearance, then Themes.
  3. Search each plugin and theme name on WPScan and note any flaw with no fixed version yet.
  4. Update everything with a fix, replace anything unmaintained, and delete anything unused.
  5. Check Dashboard, then Updates, for a pending WordPress core release.

WordPress.org notes that only the latest WordPress version is officially supported, and that its security team of more than 50 experts backports fixes to older versions only as a courtesy, on its Security page (checked November 2026). Running an old version means you may not get the next fix.

A security plugin can automate part of this work with scans and alerts. Our guide on how to set up the Wordfence firewall walks through one common option.

What mistakes should you avoid?

Avoid assuming that a small site is safe, that a paid plugin is always secure, or that updating once a month is fast enough.

Small sites are scanned by bots just like large ones, because bots do not check your traffic before they probe for known flaws. Paid plugins also carry flaws, and Patchstack found that premium components had 3 times more known exploited vulnerabilities than free ones in its 2026 report (checked November 2026).

Other common mistakes include:

  • Keeping plugins installed “just in case” instead of deleting them.
  • Using the same password on your site, your email, and your host account.
  • Ignoring update notices for weeks after a security release ships.
  • Installing plugins from unofficial download sites to save money.
  • Skipping backups because the site has never been hacked before.

Security is risk reduction, not risk elimination. The WordPress hardening guide puts it that way in its Hardening WordPress handbook (checked November 2026), and that is the right way to judge each step: it lowers the odds, even if no single step removes all risk.

Frequently asked questions

Is WordPress core itself the main security risk?

No. Patchstack counted only 6 core vulnerabilities in 2025, all low priority, while 91% of new flaws were in plugins and 9% in themes. Core still needs prompt updates, because a core flaw affects every site, but plugins and themes are where most of the risk sits.

How often should I check my plugins for vulnerabilities?

Check at least once a month, and at once when security news names a plugin you use. Heavily targeted flaws can be exploited within hours of disclosure, so a monthly check is a minimum, not a full plan. Turn on auto-updates for plugins you trust, and keep a list of what you run.

Does a security plugin fix vulnerabilities in other plugins?

No, it cannot fix the flawed code itself. A security plugin can block known attack patterns, limit logins, and alert you to a flaw, but only the plugin author can fix the code. Update the flawed plugin, or replace it if no fix exists.

Are free plugins less secure than paid plugins?

Not as a rule. Free plugins get more public scrutiny, while paid plugins are harder for researchers to test. Patchstack found that premium components had 3 times more known exploited vulnerabilities than free ones in 2025. Judge each plugin by its update history and support, not its price.

Can a firewall alone keep my WordPress site safe?

No. Patchstack tested common defences in 2025 and found that traditional defences blocked only 12% of WordPress-specific attacks in one study and 26% in a broader study. A firewall helps, but updates, strong logins, and removing unused plugins matter more.

What should I do if a plugin I need has no fix for a known flaw?

Remove it if you can, or replace it with a maintained option that does the same job. If you must keep it, put a firewall rule in front of it if one is available, limit who can reach the affected feature, and check daily for a fix. Do not leave it running and hope no one finds it.

Sources

  1. State of WordPress Security in 2026 Patchstack
  2. OWASP Top 10:2025 OWASP
  3. A01:2025 Broken Access Control OWASP
  4. A05:2025 Injection OWASP
  5. Hardening WordPress WordPress Developer Resources
  6. Security WordPress.org
  7. WPScan: WordPress Security Scanner WPScan

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.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test