Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
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
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Explainers · Explainer

What Is Brute Force Attack? A Plain Explanation

What Is Brute Force Attack? A Plain Explanation

Short answer

A brute force attack is an automated attempt to break into an account by trying username and password combinations until one works. On WordPress, bots hammer wp-login.php and xmlrpc.php, often from many computers at once. You stop it with long unique passwords, two-factor login, login limits, and blocking at the edge.

Key takeaways

  • A brute force attack tries username and password combinations automatically until one works.
  • Wordfence blocked over 55 billion password attacks against WordPress sites in 2024.
  • Bots target wp-login.php and xmlrpc.php, and xmlrpc.php can carry many guesses in one request.
  • Passwords under 15 characters are weak without MFA, and under 8 characters are weak with it.
  • Multi-factor login is by far the best defense against most password-related attacks.
  • Lockouts should count failures per account, not per IP, and locked users need a way back in.

What is a brute force attack?

A brute force attack is an automated attempt to break into an account by trying username and password combinations until one works.

The attacker does not need a clever trick. A program simply works through a list of likely passwords, one after another, until it finds the right one or gives up. The attack is named for the method: raw force, applied again and again.

WordPress's own handbook calls it the simplest way to break in, and notes that the attempts are automated and often spread across botnets, so even failed attacks can flood a site with requests.

The scale is hard to picture. Wordfence's 2024 report states that it blocked over 55 billion password attacks against WordPress sites in 2024, alongside more than 54 billion malicious requests.

How does a brute force attack work on WordPress?

On WordPress, bots hammer the login page and the XML-RPC endpoint with guess after guess, often from many computers at once.

The main target is wp-login.php, the file behind the WordPress login form. A bot sends a username and password, gets a “wrong password” reply, and tries the next pair, thousands of times an hour if nothing stops it.

The second target is xmlrpc.php, and it is worse. WordPress's handbook explains that this file is a frequent target, especially its system.multicall method, which lets many login attempts ride inside a single request and slip past simple attempt counters.

The third route is username discovery. Bots probe author pages and the REST API to learn real usernames, then aim their guesses at accounts they know exist, starting with admin.

Our guide on how to disable XML-RPC in WordPress shows how to close that second route when your site does not need it.

How is brute force different from password spraying and credential stuffing?

Brute force tries many passwords against one account, while spraying and stuffing spread the guesses across many accounts.

The three attacks look alike in a log file, but they dodge different defenses, so it helps to tell them apart. OWASP's Authentication Cheat Sheet treats them as separate patterns with separate counters.

AttackWhat the attacker triesWhat it dodges
Brute forceMany passwords against one accountNothing, if attempts per account are limited
Password sprayingOne weak password against many accountsPer-account lockout, since each account sees few failures
Credential stuffingUsername and password pairs leaked from other sitesPassword strength rules, since the leaked password may be long

A limit on failures per account stops brute force but barely slows spraying, because each account only fails once or twice. Spraying needs a limit per IP address as well, so one machine cannot test the same password against thousands of accounts.

Credential stuffing is the hardest of the three to stop with passwords alone. The pairs come from breaches on other sites, so the password may be long and pass every strength rule, and the only fix is a second factor or a check against breached lists.

Why is WordPress a common target?

WordPress is a common target because it runs a huge share of the web and its login page sits at the same address on every site.

An attacker does not need to study your site first. Every WordPress install has wp-login.php and wp-admin in the same place, so a bot can scan thousands of sites and try the same attack on each one with no changes.

WordPress's handbook notes that this is not a WordPress-only problem: every web application with a login surface can be targeted, but WordPress's popularity makes it a common focus.

The same logic applies to plugins. Wordfence's 2024 report found that plugin flaws were 96% of all vulnerabilities disclosed in 2024, with 8,223 published in total, about 68% more than in 2023.

That popularity also means the defenses are well known. The fixes in this guide are standard, documented, and cheap, which is why leaving them off is hard to excuse.

Our statistics guide on WordPress security statistics has the latest figures on attacks, flaws, and patch rates.

How do you know your site is under attack?

You know your site is under attack when failed logins spike, the server slows down, or your security plugin starts blocking addresses.

Check the failed login count first. A normal site sees a handful of failed logins a day from owners who mistype a password. An attack shows hundreds or thousands in an hour, often aimed at usernames such as admin, administrator, or your own author name.

Watch the server too. WordPress's handbook warns that even failed attacks can overwhelm a site with requests, because each guess runs WordPress and hits the database. A sudden slowdown with no traffic spike in analytics often means bots, not visitors.

Your security plugin will usually tell you plainly. Wordfence and similar plugins log each blocked address and each failed login, so open the firewall log and look for one address trying many passwords, or many addresses trying one password.

How do you stop a brute force attack?

You stop a brute force attack with a mix of strong passwords, two-factor login, login limits, and blocking at the edge.

Start with the password. OWASP's cheat sheet, citing NIST SP 800-63B, states that passwords shorter than 8 characters are weak when MFA is on, and shorter than 15 characters are weak when it is not on.

Set the maximum length to at least 64 characters, so passphrases fit. OWASP gives that figure in the same section of its cheat sheet.

Then add a second factor. OWASP states that multi-factor authentication is by far the best defense against the majority of password-related attacks. WordPress's handbook notes that WordPress core does not include two-factor login as of 2025, so you need a plugin or single sign-on to add it.

Then limit the guesses. OWASP explains that a lockout policy has three parts: a threshold of allowed failures, an observation window, and a lockout duration.

The failure counter should sit on the account, not the source IP, so an attacker cannot dodge it by switching addresses. Some apps use an exponential lockout that starts near one second and doubles after each failed login.

Finally, block the traffic before it reaches WordPress. WordPress's handbook advises preferring edge or WAF protection, such as Cloudflare or Sucuri, so bad traffic is stopped before it reaches your server.

Its Nginx example limits logins to 10 requests per minute per address, with a burst of 20, for both wp-login.php and xmlrpc.php.

Our guide on how to stop brute force attacks on WordPress walks through the plugin settings step by step.

Our guide on how to set up the Wordfence firewall covers the firewall side.

What should you do after an attack?

After an attack, change the passwords on every admin account, check for new users and files, and review your logs.

Change passwords first, starting with any account the logs show was guessed at. Use a password manager to make each one long and unique, and check each new password against a breached list.

OWASP names Have I Been Pwned's Pwned Passwords service for checking a password against lists from known breaches.

Then look for signs that an attacker got in. Check Users for accounts you did not create, and check the plugin list for plugins you did not install.

Scan the site with your security plugin. A successful login is often followed by a new admin user or a quiet file upload.

Then review the logs to see what the attack tried. WordPress's handbook advises auditing logs for failed logins and blocking abusive IPs for a time. If the same addresses keep coming back, block them at the firewall or CDN rather than in WordPress.

Our guide on how to run a WordPress security audit gives a full checklist for this review, including file checks and user checks.

What mistakes should you avoid?

Do not rely on hiding the login page, reusing one password, or locking accounts forever without a way back in.

Hiding the login page feels like a fix, but it only cuts noise. WordPress's handbook warns that obscuring the login URL can reduce noise but should not be your only defense, because the real address is easy to find.

Reusing one password across sites is the mistake that turns a small breach into a big one. If that password leaks from any other site, credential stuffing can walk straight into your WordPress admin with a correct pair.

Locking accounts forever is a trap of the opposite kind. OWASP warns that lockouts can be used to deny service to other users, since anyone who knows a username can lock that person out by failing on purpose.

Its suggested fix is to let locked-out users recover through the forgotten-password flow.

Also avoid the username admin. WordPress's handbook states plainly: do not use the username admin. Create a separate admin account and remove or demote the old one, and keep the number of administrator accounts small.

Frequently asked questions

Can a brute force attack break into any WordPress site?

Yes, if the password is weak. Bots work through lists of common passwords, and a short or reused password can fall in minutes. A long unique password plus two-factor login stops the attack even when the password is guessed, because the second factor still blocks entry.

Does WordPress have two-factor login built in?

WordPress core does not include two-factor login as of 2025, so you need a plugin or single sign-on. Wordfence, Solid Security, and the Two-Factor plugin by WordPress contributors all add it, and WordPress's own handbook recommends it for every administrator account.

Is hiding the login page enough to stop brute force attacks?

No. Hiding the login page only cuts noise, because the real address is easy to find. WordPress's handbook warns that it should not be your only defense. Use it as an extra layer, on top of login limits and two-factor login.

What should I do if a brute force attack succeeds?

Change the passwords on every admin account, then check Users for accounts you did not create and check the plugin list for plugins you did not install. Scan the site with your security plugin and review the login logs to see what the attacker tried.

Are brute force attacks still common in 2026?

Yes. Wordfence blocked over 55 billion password attacks in 2024, but its report also notes that password attacks overall are on the decline, while attacks aimed at software flaws are rising. Keep plugins updated as well as locking down logins.

Sources

  1. Brute Force Attacks WordPress Developer Resources
  2. Authentication Cheat Sheet OWASP
  3. 2024 Annual WordPress Security Report Wordfence
  4. Pwned Passwords Have I Been Pwned

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

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.