Bad Login Attempts

What It Does

Limit Login Attempts counts failed sign-ins and temporarily bans the IP address once the limit is reached.

The counter is the same for a real account and for an identifier that matches no account (username or email address). An unknown identifier is counted even when Forbid User Enumeration is off, and it is not stored in clear text. There is no block on the first try.

Each failed authentication inside the same XML-RPC request is counted. Once that request reaches the limit, the IP address is banned immediately.

When 3 attempts or fewer remain, the login page says so. At the limit, the IP address is banned for the configured length of time.

Why It Matters

Brute-force attacks try identifiers in bulk, including names that do not exist. Counting those separately, or blocking them immediately, either lets the volume through or reveals that an account is missing.

One limit treats a typo and an invented attempt the same way.

How to Use

Open the Users & Login module, Login Control section.

Enable Restrict bad login attempts (Brute Force).

The attempt count and the ban length are no longer on this screen. They appear only in Expert Mode, in the same section: 2 to 25 attempts (5 by default, 5 to 25 recommended) and 1 to 60 minutes (5 by default, 5 to 15 recommended).

A successful sign-in resets that account’s counter. Allowed IP addresses are not counted.